In the Notification Settings tab of the Account Settings page, you can configure webhooks to fire each time data is loaded into your existing destination. Using Stitch’s post-load hooks feature, you can automate your post-load processing functions.

In this guide, we’ll cover:

Uses for post-load hooks

Using post-load hooks, you can trigger:

For technical details about post-load hooks, refer to the Post-load webhooks reference.

Access to post-load hooks

The post-load hook feature is available during the Free Trial or on an Advanced or Premium plan. Contact Stitch Sales for more info about these plans.

The post-load hook feature is available during the Free Trial or on an Enterprise plan. Contact Stitch Sales for more info about Enterprise plans.

Plan downgrades

If you decide to downgrade to a plan without post-load hook access, the feature will be disabled and notifications will no longer be sent to the webhook URLs in the post-load hook list.

If you upgrade from a plan without post-load hook access to a plan that includes it, and you previously added post-load webhook URLs in your account, you will need to re-enable them to allow Stitch to send webhooks to the webhook URLs again.

Post-load hook basics

How many post-load hooks can I have?

An account’s post-load hook list may have a maximum of 10 webhook URLs.

How are webhooks sent?

Post-load webhooks are sent on a per-integration, per-table basis.

For example: You’re tracking two tables (orders and customers) in a Shopify integration. Stitch will send two post-load webhooks for the Shopify integration - one for the orders table, and one for customers.

When are webhooks sent?

A post-load hook will be sent each time data for a tracked table is successfully loaded or rejected.

Note: In the event that Stitch is unable to deliver the webhook to the URL(s) in the Post-load hook list, an email notification will be sent.

What services can I use with post-load hooks?

To be compatible with Stitch post-load hooks, the service must provide a properly formatted HTTPS webhook URL.

Manage post-load hooks

Any team member in a Stitch account that has access to the post-load webhook feature can create, delete, disable, or re-enable a post-load webhook URL.

You can manage post-load webhooks in two ways:

  1. In the Stitch app:

  2. Via the Connect API, if your Stitch plan includes API access.

Add a post-load webhook URL in the Stitch app

To add a post-load webhook URL:

  1. Click the User menu (your icon) > Edit User Settings.
  2. Click the Notification Settings tab.
  3. Click the Add Webhook button in the Post-load hooks section.

  4. In the field that displays, paste the webhook URL.

    Note: The webhook URL must use HTTPS, otherwise you’ll receive an Invalid URI error and be unable to save the webhook.

  5. Click the Save Webhook button.

Delete a post-load webhook URL in the Stitch app

To delete a post-load webhook URL:

  1. Click the User menu (your icon) > Edit User Settings.
  2. Click the Notification Settings tab.
  3. Scroll to the Post-load hooks section.
  4. Click the icon next to the Status column.
  5. Click Delete this webhook.
  6. You’ll be prompted to confirm the deletion. Click Delete to continue and delete the webhook URL.

Disable or re-enable post-load webhook URLs in the Stitch app

If you want to temporarily disable a post-load webhook, you can click the icon next to the webhook URL and use the Disable this webhook option.

To re-enable a disabled webhook URL, click the icon next to the Status column and select Re-enable this webhook.

Post-load hook technical reference

Refer to the Post-load webhooks reference for detailed info about:

  • Data included in request headers and bodies
  • Retries
  • Security
Related Troubleshooting
Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.