REST Hook triggers are marked as Instant in the Zap editor.

When building in the Platform CLI, use the example implementation for guidance.

With a REST Hook trigger, Zapier subscribes to your server using a unique URL per activated Zap and your app sends a payload of data back to the unique URL to trigger that particular Zap whenever that trigger event occurs in your app.

REST Hooks differ from static webhooks. With static webhooks, your customer needs to manually copy and paste a specific URL per Zap to connect your app and their Zap together, whereas with REST Hooks this is all handled automatically for them between Zapier and your app.

Zapier does not support Identity Confirmation for webhook subscriptions.

​

Prerequisites

• Your app supports REST Hooks - webhook subscriptions that can be manipulated through a REST API.
• A way to store the unique URLs we send you, such as a database.
• A way to send payloads in JSON format to each stored URL, when a specific event happens that you want to trigger the associated Zap on.
• One or more endpoint(s) to receive subscribe and unsubscribe payloads (these can be the same endpoint(s) or separate ones)
• If your webhook subscriptions expire, make sure the subscribe endpoint returns an expiration_date property containing an ISO8601 date. The platform will automatically attempt to resubscribe after the expiration date.

When a Zap is turned on, the subscribeHook function is called with a payload of data that includes the unique URL to send data to in order to trigger the Zap. Store this URL, associating it with an id and use it whenever you want to trigger this Zap. Return that id in the response back to Zapier to be used later in the Unsubscribe.

When the Zap is turned off, the unsubscribeHook function is called to notify your app to delete the unique URL previously stored for this Zap.

​

1. Write the subscribeHook Function

The first function to implement is the subscribeHook function which provides the URL you will use to trigger the Zap. Include the following parameters:

• url should be bundle.targetUrl which is an URL Zapier automatically generates for each activated Zap.
• Any other data you want to send from any inputFields

const subscribeHook = (z, bundle) => {
  const data = {
    url: bundle.targetUrl,
    field: bundle.inputData.field,
    // etc
  };

  const options = {
    url: 'subscription endpoint url',
    method: 'POST',
    body: data
  };

  // make the request and parse the response - this does not include any error handling.
  return z.request(options)
    .then((response) => response.data);
}

This function is called in the performSubscribe method on the module for the Trigger:

module.exports = {
  // Other data about the Trigger, e.g. key, name, etc. omitted
  performSubscribe: subscribeHook
};

This function will run every time a Zap is turned on.

​

2. Write the unsubscribeHook Function

The next function to implement is the unsubscribeHook function which will be called when a Zap is turned off. This notifies your servers to delete the URL you’ve been storing and stop sending payloads to it. If your API continues posting notification payloads to the Zap after it has unsubscribed, you can expect to see a 410 response from Zapier.

bundle.subscribeData.id is required — this is the ID of the hook in question. You could assign it to a hookID variable or similar.

Include the following parameters:

const unsubscribeHook = (z, bundle) => {
  // bundle.subscribeData contains the parsed response JSON from the subscribe request.
  const hookId = bundle.subscribeData.id

  const options = {
    url: `unsubscription endpoint url/${hookId}`,
    method: 'DELETE'
  }

  return z.request(options)
    .then((response) => response.data);
};

This function is called in the performUnsubscribe method on the module for the Trigger:

module.exports = {
  // Other data about the Trigger, e.g. key, name, etc. omitted
  performUnsubscribe: unsubscribeHook
};

A REST Hook trigger missing a Subscribe or Unsubscribe function, is presented to users as a Static Webhook. Static hooks are not supported in public integrations, but they could be used if the integration intends to remain private.

​

3. Write the perform Function

The next function to implement is the perform function which is called each time your app delivers a notification payload to Zapier. This is what actually triggers the Zap. Typically, you would simply return the cleaned request in an array. The data returned by the request must be an array.

const parseHookPayload = (z, bundle) => {
  // bundle.cleanedRequest will include the parsed JSON object (if it's not a
  // test poll) and also a .querystring property with the URL's query string.
  const payload = {
    id: bundle.cleanedRequest.id,
    name: bundle.cleanedRequest.name,
    directions: bundle.cleanedRequest.directions,
    style: bundle.cleanedRequest.style,
    authorId: bundle.cleanedRequest.authorId,
    createdAt: bundle.cleanedRequest.createdAt
  };

  return [payload];
};

followed by:

module.exports = {
  // Other data about the Trigger, e.g. key, name, etc. omitted
  perform: parseHookPayload
};

​

4. Write the performList Function

The final function to implement is the performList function, used when testing the Trigger to collect sample data in the Zap editor. Though optional, not defining a performList is a sub-optimal experience for users and is required for public apps.

Most commonly this is a GET request to an endpoint of your API which will provide a response from the user’s account with the exact same schema as the data delivered via webhook when a trigger event happens.

Response data returned must be an array, even if the array contains only one object. It must have the exact same schema as the data delivered via webhook when a trigger event happens otherwise fields mapped from this sample in subsequent steps of a Zap will break when it runs live.

const getFallbackSample = (z, bundle) => {
  // For the test poll, you should get some real data, to aid the setup process.
  const options = {
    url: 'sample endpoint here',
    method: 'GET',
    params: {
      style: bundle.inputData.style
    }
  };

  return z.request(options)
    .then((response) => response.data);
};

followed by:

module.exports = {
  // Other data about the Trigger, e.g. key, name, etc. omitted
  performList: getFallbackSample
};

​

5. Test your API Request

To test the REST Hook trigger, build a Zap in the editor.

​

6. Define sample and outputFields

Define sample data and output fields following the guide. You can see an example of this here.

​

BasicHookOperationSchema

​

subscribeHook

Function that sends a payload of data to an endpoint you control. You need to grab the targetUrl parameter and store it securely as this URL is used to send data from your app to Zapier when the triggering event occurs, and thus trigger the Zap. You can see an example of this here.

​

unsubscribeHook

Function that calls an endpoint you control with a payload of data, including the targetUrl parameter. You need to deactivate or delete the URL from your storage completely as the Zap associated will no longer trigger when requests are made to it. If your API continues posting notification payloads to the Zap after it has unsubscribed, you can expect to see a 410 response from Zapier. You can see an example of this here.

​

perform

This should be a function that processes the inbound webhook request. No HTTP request has to made here. As seen in the example app here, this can simply take the data from bundle.cleanedRequest and build a new object that is returned within an array. It’s important to return this object within an array as specified here.

​

performList

Testing a REST Hook trigger in the Zap editor will only call performList, not perform. performList ideally should make a HTTP request to an endpoint that can return sample data to be mapped into subsequent steps of the user’s Zap. You can see an example of this here. Required for public apps and highly recommended for private apps to avoid user confusion when setting up a Zap.

Need help? Tell us about your problem and we’ll connect you with the right resource or contact support.