Language:日本語|EN
Categories

Introducing support for manual Webhook triggers from the Shifter Dashboard

There are many features in Shifter Static that were born out of your feedback, Webhooks is one of them. With this update, you can now use webhooks in a more flexible way, so let’s review the features and see what’s new.

We’d love to hear what you think of the new features and how you can implement them in your operations. If you try out this feature and have feedback, let us know.

Let’s take a look at the new features and how you can use them.

What are Shifter Webhooks?

There are two types of Webhooks on Shifter. One for when the generator starts and another for when WordPress starts. These two lifecycle events are helpful to create custom notification, extensions, or 3rd party integrations such as IFTTT and Zapier. Most integrations using Shifter Webhooks are possible without writing a single line of code.

Manually triggering Webhooks

The phrase, “Outgoing Webhook at Generate” is a feature that allows you to deploy static sites (Artifacts) to external services and environments. This feature release is an extension of that. By adding support for manually triggering some Webhooks we have control over our sites and actions.

How to access manual Webhooks from the Shifter Dashboard

Select Artifact in the Deploys list and click Detail.

Navigate to the details and scroll down the page to find the Webhook block.
Click Invoke Webhook to configure it.

Previously, “Outgoing Webhook at Generate” was a one-time feature that would run once the Artifact creation was complete.

With this update, you can now manually deploy the required Artifacts again. With this feature, you can easily reuse the same Artifacts or roll back to a previous version without hassle.

Use cases

Deploy to an external web hosting service such as Netlify. You can work with other 3rd party hosting providers too. Since Webhooks are a widely accessible format there is a lot of flexibility.

Meeting unique policy requirements such as storing backups. You can store artifacts outside of Shifter to be in compliance.

Support documentation

Shifter Outgoing Webhooks at Generate: https://support.getshifter.io/en/articles/2864243

Resend or send webhook manually: https://support.getshifter.io/en/articles/4542379-resend-or-send-webhook-manually

Using Shifter Outgoing Webhook at Generate with Netlify: https://support.getshifter.io/en/articles/2863291-using-shifter-outgoing-webhook- at-generate-with-netlify

Shifter Webhooks: https://support.getshifter.io/en/collections/1667536-shifter-webhooks

Related Documents

Official blog on deploying webhooks to Netlify: https://www.digitalcube.jp/shifter/8619/

User blog: https://qiita.com/biatunky/items/8655fee1877163aa51a3

User blog: https://riotz.works/articles/lulzneko/2019/12/24/first-website-with-shifter-webhooks-and-gridsome-on-netlify/

Availability

The manual triggers feature for Shifter Webhooks is available now for all Tier 2 plans. Tier 2 is one our most popular plans for its wide range of business use cases.

If you have any questions, please feel free to contact us via our support chat.

Recent posts

Introducing PHP Error Logs

Say hello 👋

Join our newsletter

Company