- A webhook: Squad gives you a URL. Another app, such as GitHub, Stripe, Zapier, or your own code, sends events to it.
- An event in a connected app: for example a new email in Gmail or a new issue in GitHub, on an account that you connected.
Before you start
- To create, change, turn on, pause, or delete triggers, you must be the owner or an Administrator. These are the same people who can save routines. An Administrator who is limited to some teammates manages only the triggers of those teammates. See Invite people to your squad.
- Collaborators and Viewers can read the triggers of the teammates they can use, under When something happens. They do not see webhook URLs, secrets, the settings of an app event, or what each event contained.
- For an app event trigger, connect the account yourself first. Only accounts that you connected are offered. See Connect apps.
Add a webhook trigger
Open Routines
Start a new trigger
Choose a webhook
Name it
Pick the teammate
Write the instructions
Pick the sender
Add the sender's secret (Stripe, Shopify, Standard Webhooks)
Choose the accounts (optional)
Set more settings (optional)
Create the trigger
Choose the sender
webhook-id, webhook-timestamp, and webhook-signature headers. Some senders that sign this way give these three headers other names. Since November 15, 2026, Squad accepts those names too. Before, it refused their requests. A request must use one set of names for all three headers. On Squad for Mac, the hint says “apps” instead of “senders” from version 1.0.116.
More settings
- Only send these fields (optional): one field path per line, such as
issue.titleordata.object.amount. The teammate then gets only those fields. Leave it empty and the teammate gets the whole event. The teammate can still read the full event when it needs to. - Most runs per day: how many runs the trigger can start each day. Events past the limit are kept, not run. You can run them from the trigger’s page. For the default and the highest value, see Limits and defaults.
- Send the result to a URL (optional): an HTTPS address where Squad posts the result of each run. See Get the result back in your app.
Set up the sender
On the trigger’s page, Where events come from shows the URL, with Copy and New URL. Under Set up the sender, Squad shows the steps for your sender, with your URL already in them. For GitHub and HMAC signature, the secret is hidden. Select Show to see it, and the steps then include it. Select Copy to copy it. Each Copy on the trigger’s page says Copied for a moment once it is copied.- URL only
- GitHub
- Stripe
- Shopify
- Standard Webhooks
- HMAC signature
- Zapier: add a Webhooks by Zapier action and choose POST. Set the URL to your trigger’s URL and the payload type to JSON. Map the fields that your teammate needs, and test the step.
- Make: add an HTTP module and choose Make a request. Set the URL to your trigger’s URL, the method to POST, and the body type to JSON. Put the fields that your teammate needs in the request content.
- n8n: add an HTTP Request node with the method POST. Set the URL to your trigger’s URL and send the body as JSON.
- Your own code: send a POST request with a JSON body to the URL. Optional: send an
Idempotency-Keyheader, so a request that you retry runs once.
Idempotency-Key header.
Add the secret from a chat card
When a teammate sets up a trigger that checks Stripe, Shopify, or Standard Webhooks signatures, it can ask you for the sender’s secret with an A secret to add card in your direct conversation with it. The secret goes onto the trigger, the same as a save on the trigger’s page. It is never posted in the chat, and the teammate never sees it. Only the owner, or an Administrator who works with the trigger’s teammate, can paste it. People who can see that teammate’s routines but cannot change them see “The squad’s owner or an Administrator can add it.” Others see only the teammate’s words.Find the card
Paste the secret
Save it
- “Waiting for the next event from the sender.” until a request comes.
- “An event came through” and the time, once a request signed with this secret was accepted. A test event does not count.
- “Squad refused a request” with the time and the reason, with Paste it again. See Troubleshooting.
- After Paste it again, Cancel closes the field again.
- After the save, the card says “Secret saved on” and the trigger’s name with the time, then “Waiting for the next event from the sender.”, “An event came through” and the time, or “The last event was turned away” with the time and the reason.
- A person who cannot see the trigger reads “Secret saved on the trigger” once it is saved, and otherwise “This trigger is no longer here.”
Send a test event
On the trigger’s page, select Send test event. Squad sends an example event. For GitHub, Stripe, and Shopify, it is shaped like the sender’s own events. For other senders, it is a short test message. It wakes the teammate for real, and the teammate is told that it is a test. The event shows with a Test tag under Latest events. Send test event works only while the trigger is on.Get the result back in your app
When you set Send the result to a URL (optional), Squad posts a JSON body to that URL each time a run ends. No result is sent when the teammate was woken but no run started. The URL must start withhttps:// and use a public host name.
The body holds the trigger’s ID and name, the run’s ID and status, the events in the run, and result, a short summary of the teammate’s final reply. See Limits and defaults. Squad signs it in the Squad-Signature header as t=<unix time>,v1=<signature>. The signature is the HMAC-SHA256 of <t>.<body> with the trigger’s callback signing secret, in hex. To copy that secret, select Copy its signing secret next to Result sent to on the trigger’s page.
If Squad cannot deliver the result, the event says “The result was not delivered to your callback URL” and the reason.
Add an app event trigger
Open Routines
Start a new trigger
Choose an app event
Name it and pick the teammate
Write the instructions
Pick the account
Pick the event
Fill in the event's settings
Choose the accounts and more settings (optional)
Create the trigger
- You cannot change the account or the event later. To listen for a different event or account, create a new trigger.
- If you have no connected accounts, the form says “You haven’t connected an account yet. Connect one, then come back.” Select Connect an app to connect one.
- If the app offers no events, the form says “This app has no events Squad can listen for yet.”
- If an event needs a setting that the form cannot show, the form says so and you cannot save. Pick another event, or ask your teammate to suggest the trigger with those settings.
Turn on a trigger that a teammate suggests
Teammates can suggest triggers, for example when you ask for work to be done each time something happens. A suggestion does nothing until the owner or an Administrator turns it on. When a teammate works for the owner or an Administrator, it can also set up a webhook trigger itself instead of suggesting one, turn on a webhook suggestion that you ask it to turn on, and change, pause, turn on, test, or delete triggers. It gives you the new trigger’s URL, and its secret when Squad made one, or puts them into the sending app. An app event trigger is always a suggestion, because it listens on the account of the person who turns it on. A teammate cannot turn one on, and a teammate’s or another person’s account for the app is not enough: the owner or an Administrator turns it on with their own account for that app. For a trigger that checks Stripe, Shopify, or Standard Webhooks signatures, the teammate asks you for the sender’s secret with a card in your conversation, and you paste it there or on the trigger’s page. See Add the secret from a chat card and Triggers.Open the suggestion
Change it if needed (optional)
Turn it on or delete it
- A webhook suggestion has no URL until you turn it on. Then set up the sender. See Set up the sender.
- An app event suggestion listens on your own account for that app. If your own account for that app is not connected, or its sign-in expired, the page says “It listens on your own [app] account, which isn’t connected yet. Connect it, then turn this on.” Connect [app] then shows instead of Turn it on, and it opens the app’s connect on Apps. Edit first and Dismiss still show. When you have connected it, Turn it on shows.
- On the page of a suggested app event, Where events come from says that the app sends the event “on the account of whoever turns it on”.
- Unless you chose otherwise with Edit first, the trigger’s runs use your own accounts and the shared ones.
Pause, change, or delete a trigger
Open the trigger from Routines: select its row under When something happens. Then:- If you change Who sends it, the secret changes with it. For GitHub or HMAC signature, Squad makes a new secret. Put it in the sender. For Stripe, Shopify, or Standard Webhooks, the trigger shows Needs a secret until you paste the sender’s secret. URL only has no secret.
- A paused webhook trigger still receives events. It keeps them as “Not run: the trigger was paused”, and wakes no one. Turn the trigger on, then select Run now on an event to run it.
- When you pause an app event trigger, Squad asks the app to stop sending that event, so events that happen while it is paused usually do not arrive. This does not apply while another trigger listens for the same event on the same account.
- Pausing also stops events that were waiting or being retried. Turn the trigger on, then use Run now or Retry.
- Squad sends no bell notification or email for suggested triggers, paused triggers, or failed events. Check Routines.
- When you pause a teammate, its triggers stay on. Their events wait as “Held while the teammate is paused”, and Squad delivers them when you resume the teammate. See Add, change, and pause teammates.
- When a teammate is removed, its triggers pause. Give them to another teammate, then turn them on.
What a trigger run looks like
Each time an event arrives, Squad wakes the teammate with the trigger’s instructions and the event. A trigger runs one run at a time. Events that arrive during a run wait, and the next run gets them together. For how many events one run can carry, see Limits and defaults.- In History, a trigger run is its own row. Its title is “Webhook:” or “App event:” followed by the trigger’s name. In the filters, Triggers under Kind shows or hides these runs. See See what your squad did.
- On the trigger’s page, the line under the name shows the last event and today’s events and runs.
- Latest events lists the newest events, each with what became of it, such as Done, Teammate working, or Could not wake the teammate. For every outcome, see Statuses. With no events yet, it says “Nothing has arrived yet. Events show here as they come in.”, or “Nothing has arrived yet. Turn it on to start taking events.” while the trigger is off.
On Squad for Mac
On Squad for Mac, triggers are in the List view of Routines, under When something happens. Triggers work the same, but some labels differ:Check that it works
- Select Send test event. Under Latest events, the test event moves to Done.
- Select Open in History on the event to see the teammate’s run in History.
- Send a real event from the sender. It shows under Latest events with a one-line summary, such as the sender’s event name.