Triggers

Custom Webhook Triggers

Fire a trigger from any system that can send an HTTP request, not just a connected app.

A custom webhook trigger doesn't watch a connected app at all — it fires when something sends an HTTP request to a URL Pushable gives you. This lets you connect a trigger to any system that can make an outbound HTTP call, including internal tools or services that aren't available as a connected integration.

Setting Up a Webhook Trigger

Choose the custom webhook type

When creating a trigger, pick Custom webhook instead of a connected app. This type has no app or event to choose — it's driven purely by whatever request arrives.

Choose the agent to run

Pick which agent should react whenever the webhook is called.

Write the instruction

Describe what the agent should do each time the webhook fires. Whatever data the incoming request carries is passed along for the agent to use.

Name it and create

Give the trigger a name and click Create trigger. Pushable generates a unique URL and a secret key for this trigger.

Firing the Trigger

To fire the trigger, send an authenticated POST request to the generated URL, including the secret key. Pushable checks the key before running anything — a request without the correct key is rejected and the agent never runs. If the key is ever exposed, you can regenerate it, which immediately invalidates the old one.

💡Tip

If the system sending the webhook retries a delivery — for example after a timeout — Pushable recognizes the duplicate and treats it as a safe no-op instead of running the agent a second time. You don't need to build your own deduplication logic on the sending side.

Everything else works the same as a connected-app-event trigger: it shows up alongside your other triggers on the Triggers tab, can be enabled, disabled, edited or deleted (see Managing Triggers), and every firing is recorded on the Trigger Runs tab.