Skip to main content
A trigger is a standing instruction to one teammate, like a routine, but an event starts it instead of a clock. When the event arrives, the teammate starts a run and does what the trigger’s instructions say. For work that runs at set times, see Schedule recurring work with routines. There are two kinds of trigger:
  • 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.
Triggers are on the Routines page, under When something happens, below your routines. The section shows when at least one trigger exists. To open Routines, see Open Routines. Squad for Mac has the same triggers, with some other labels. See On Squad for Mac.

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

1

Open Routines

Open Routines. See Open Routines.
2

Start a new trigger

Select New routine, then When something happens. The New trigger form opens.
3

Choose a webhook

Under What should wake the teammate?, select A webhook.
4

Name it

In Name, type a short name, for example “New GitHub issue”.
5

Pick the teammate

In Teammate it wakes, select the teammate.
6

Write the instructions

In What the teammate does with each event, write what the teammate must do with each event. The teammate gets these instructions with every event. The event itself is treated as data, never as instructions. When they name a skill or a file on your cloud computer, a chip under them shows it by name. See Skills and files named in instructions.
7

Pick the sender

In Who sends it, select the app that sends the events. See Choose the sender.
8

Add the sender's secret (Stripe, Shopify, Standard Webhooks)

For Stripe, Shopify, or Standard Webhooks, paste the secret from the sender into Stripe signing secret, Shopify client secret, or Signing secret. If the sender shows the secret only after you add the URL, leave the field empty and add the secret later on the trigger’s page, or in the chat card when a teammate asks for it.
9

Choose the accounts (optional)

If your squad has or had other people in it, choose in Accounts the teammate may use while it works: Mine and the shared ones or Only the shared ones. See Choose the accounts of a routine. The same rules apply.
10

Set more settings (optional)

Open More settings to limit the fields, set Most runs per day, or send the result to a URL. See More settings.
11

Create the trigger

Select Create trigger.
The trigger’s page opens. It shows the trigger’s URL and the steps to set up the sender. The trigger shows On, or Needs a secret when the sender is Stripe, Shopify, or Standard Webhooks and you did not paste the secret yet. Add the secret once the sender shows it. Continue with Set up the sender.

Choose the sender

Standard Webhooks reads the signature from the 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.
With Stripe, Shopify, or Standard Webhooks, Squad refuses every request until you add the secret. The trigger shows Needs a secret until then.

More settings

  • Only send these fields (optional): one field path per line, such as issue.title or data.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.
Pick your tool with Zapier, Make, n8n, or Your own code, and follow its steps:
  • 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-Key header, so a request that you retry runs once.
When a sender delivers the same event again with the same delivery ID, Squad keeps it once and runs it once. Squad reads the ID from GitHub, Shopify, and Standard Webhooks headers, from the Stripe event ID, and from an 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.
1

Find the card

In the conversation, find the card with A secret to add. It names the field and the trigger, for example Stripe signing secret for and the trigger’s name.
2

Paste the secret

Copy the secret from the sender and paste it into the card’s field. The card says “Goes straight onto the trigger. The chat never sees it.”
3

Save it

Select Save to trigger. Squad posts “I saved the signing secret on the trigger.” as your reply, so the teammate knows.
The card then shows Secret saved on and the trigger’s name, and what the trigger did with the next event from the sender:
  • “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.
If you already pasted the secret on the trigger’s page, the card says “A secret is already saved on this trigger. Paste a new one to replace it.” Select It’s saved to tell the teammate without pasting it again. Not now closes the card, and the teammate is not told. On Squad for Mac and on Squad for iPhone and iPad, from version 1.0.117, the card has the field, Save to trigger, It’s saved, and Not now, as on the web. Its differences:
  • 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.”
Older versions show “This message includes a trigger_secret card. Update Squad to interact with it.” on the Mac, and only the teammate’s words on iPhone and iPad.

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 with https:// 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

1

Open Routines

Open Routines. See Open Routines.
2

Start a new trigger

Select New routine, then When something happens.
3

Choose an app event

Under What should wake the teammate?, select An event in a connected app.
4

Name it and pick the teammate

In Name, type a short name. In Teammate it wakes, select the teammate.
5

Write the instructions

In What the teammate does with each event, write what the teammate must do with each event.
6

Pick the account

In Account, select one of your accounts. Only the accounts that you connected yourself are listed.
7

Pick the event

In Event, select the event. The list comes from the app, so each app offers its own events.
8

Fill in the event's settings

Some events have settings, such as a label or a channel. Fill in the required ones. Fields marked (optional) can stay empty, and the app then uses its own default.
9

Choose the accounts and more settings (optional)

If your squad has or had other people in it, choose in Accounts the teammate may use while it works. Open More settings for the other options. See More settings.
10

Create the trigger

Select Create trigger.
The trigger’s page opens. While Squad asks the app to send the event, the trigger shows Connecting and the page says “Squad is asking the app to send this event. This usually takes a few seconds.” Then it shows On. There is no URL to set up. On the trigger’s page, Where events come from says which app sends which event, and on whose account, for example “GitHub sends a new issue on an account you connected.” Below that, it lists the settings that the trigger was saved with, for example the owner and the repository of a GitHub event. Each setting name shows as words, for example Repo name. A yes or no setting shows Yes or No. A setting that you left empty is not listed, because the app uses its own default.
  • 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.
Ask your chief of staff
A suggestion shows first under When something happens, with the line “[name] suggests this. It stays off until it’s turned on.” Its status is Suggested. Its page says “[name] suggests this trigger. It does nothing until you turn it on.” Squad tells the teammate to let the owner or an Administrator know where it waits. On Squad for Mac, suggestions also show in Needs you. See Answer what needs you.
1

Open the suggestion

On Routines, under When something happens, select the suggestion. The page says which teammate suggested it, and why when the teammate gave a reason.
2

Change it if needed (optional)

Select Edit first, change the fields, and select Save changes.
3

Turn it on or delete it

Select Turn it on. To turn it down instead, select Dismiss. The question “Dismiss this suggestion?” opens. Select Dismiss to confirm.
After you turn it on, the trigger is on. Until it is ready, it can show Needs a secret (a webhook that needs a pasted secret) or Connecting (an app event).
  • 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:
Delete cannot be undone. The trigger’s event history is deleted with it, and a webhook URL stops answering at once.
  • 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.
In Latest events: Run now, Retry, and Send test event are not held back by Most runs per day. Squad keeps events and their payloads for a limited time. See Limits and defaults.

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: On the Mac, Where you send from picks the tool whose setup steps show, for example Zapier or your own code. People who cannot change triggers do not see the address, the secret, or what an event carried, the same as on the web.

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.

Troubleshooting