Skip to main content
An app event trigger runs your script when something happens in one of your connected apps. Instead of checking a tool yourself or starting a script by hand, you pick the event you care about — a new Slack message, a Calendly booking, an issue opened in Linear — and Script.it runs the script the moment it happens.

​
Before you start

Connect the app first. Only apps you’ve connected show up in the trigger list. You can connect from Settings → Integrations, or just ask the agent — it’ll prompt you when a connection is missing. See Connecting integrations.
A trigger uses the account you connected. If that connection is removed or expires, the trigger stops firing until you reconnect. Script.it flags affected triggers so you can spot them.

​
Creating an app event trigger

1

Open the Triggers tab

Open the script you want to run, click the Triggers tab, then click Add Trigger.
2

Find the event

Search the list for the app or the thing you want to watch for — type “pull request”, “new row”, or “Slack”. The list shows events for the apps you’ve connected.
3

Pick the account

If you’ve connected more than one account for that app, choose which one the trigger should watch.
4

Fill in the settings

Most events have a setting or two to narrow them down — which Slack channel, which Notion database, which spreadsheet, which Gmail search to match.
Narrow the trigger as much as you can. A Gmail trigger scoped to one sender is more useful, and cheaper to run, than one that fires on every incoming message.
5

Choose the script

Pick the script to run, and fill in any inputs it needs.
6

Create the trigger

Click Create Trigger. It starts watching straight away.
Or skip all of that and describe it in chat: “Run this whenever a new row is added to the Q3 leads sheet.”

​
Available events

This list isn’t a limit. If your app isn’t here, or the event you want isn’t in the list, you can still trigger on it. Connect the service as a custom integration — any REST API works — and ask the agent to build a custom trigger that watches it. The result behaves exactly like a built-in event: it lives in your script, has its own settings and run history, and travels with the script when you share it.
The events below are ready to use out of the box — over 80 across these apps: We add to this regularly, so the list in the app is always the current one — check there first, and build a custom trigger for whatever isn’t in it yet.

​
How quickly a trigger fires

It depends on the app:
  • Instantly — apps that notify Script.it directly the moment something happens. Slack, GitHub pushes, Stripe, Linear, Jira, Trello, Asana, Zoom, and Shopify orders work this way.
  • On a regular check — for everything else, Script.it checks the app periodically and runs your script when it finds something new. Expect a short delay rather than an instant reaction, and a slightly longer one for triggers that have been quiet for a while.
Either way you don’t have to configure anything — each event already uses the fastest method its app supports.

​
Email your agent

Agent Email is a trigger too: your agent gets its own email address, and mail sent to it can run a script. Useful for forwarding things in — a receipt to file, a report to summarize, a request to act on.

​
What your script receives

When the trigger fires, the event’s details are handed to the script — the message text, the issue title and body, the row that was added, whatever the app sent. Your script can read those values and act on them. If the script produces files, they’re available in that run’s session, just like a run you started yourself.

​
Managing app event triggers

Turn a trigger off and on from the script, and check its recent runs there too. See Managing triggers for run history, failures, and limits.