Trigger links and incoming events

An automation that reacts to outside events has a trigger link: a URL like https://clickruntime.com/in/…. Any service that can send an HTTPS POST to a URL (Stripe, GitHub, Shopify, Typeform, form tools, your own code) can trigger it.

Set it up#

1. Ask your assistant for the automation, for example "When a Stripe payment succeeds, post it to #sales".
2. Copy the trigger link from the chat or from the automation page.
3. Paste it into the sender's webhook settings. For Stripe that's Developers → Webhooks → Add endpoint.
4. If the sender gives you a signing secret, save it as a secret (for example STRIPE_WEBHOOK_SECRET) on Connections & secrets.
5. Let the assistant turn it on and send a test event.

While the automation is a draft, events that arrive are stored so you can see them, but they don't run anything. Once live, each event runs the script.

Verify signatures#

Anyone who knows the URL can send to it, so check that each request really comes from the sender. Your assistant usually sets this up when it creates the automation. To set it yourself, open the automation page and go to Signature check under Trigger link:

1. Under Sender, choose Stripe, GitHub, Shopify, Typeform, Standard Webhooks (Svix and others) or Generic HMAC-SHA256.
2. Under Signing secret, choose the secret that holds the sender's signing secret. If it isn't saved yet, select Add it as a secret.
3. For Generic HMAC-SHA256 only, you can also set the Signature header, the Encoding (hex or base64) and a Prefix that comes before the signature. Leave them empty to use common defaults.
4. Turn on Require signature and select Save signature settings.

With Require signature on, requests that fail the check are rejected and never reach your script. In Recent events they're marked Rejected: signature invalid, and requests that pass are marked Verified. With it off, every request still runs the script, and the ones that fail are marked Signature failed. Test events sent from the automation page skip the check. See the script reference for the headers each sender uses.

Retries and retention#

If the platform fails or a run times out, an incoming run is tried again up to 3 times in total. Script errors are retried only if you turn that on under Retries on the automation page. Incoming events are kept for 30 days and run logs for 90 days.

Send a test event#

On the automation page, select Send a test event, edit the JSON body and send. You'll see the event and the run it produced. The Recent events list shows what arrived, with sensitive headers masked.

Two patterns#

• Each event performs the action: a payment arrives, a message goes out.
• Events are remembered and the action runs on a schedule: collect submissions all day, send one digest at 6pm.

The automation's summary says which one it uses.