Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.script.it/llms.txt

Use this file to discover all available pages before exploring further.

An integration event trigger fires your script automatically when a specific event occurs in one of your connected tools. Instead of polling for changes or manually kicking off a script, you define the event you care about — a new Slack message in a channel, a Calendly booking, an incoming Gmail email, a new Linear issue — and Script.it runs the configured action the moment it happens.

​
Prerequisites

Before you can create an integration event trigger, you need to connect the relevant integration to your Script.it account. If you haven’t done that yet, go to the Integrations section and authenticate the tool you want to use.
Each integration event trigger requires an active connection to the corresponding tool. If you disconnect the integration later, the trigger will stop firing until the connection is restored.

​
Creating an integration event trigger

1

Open the Triggers tab

Open the script you want to trigger from an integration event. Click the Triggers tab, then click Add Trigger.
2

Name the trigger and choose Integration Event

Enter a descriptive name for the trigger — something that identifies the source and event, like “New Calendly booking” or “Linear issue assigned to me”. In the Trigger Type dropdown, select Integration Event.
3

Select the integration

Use the Integration dropdown to choose the connected tool you want to listen to — for example, Slack, Gmail, Calendly, or Linear. Only integrations you’ve already connected will appear here.
4

Choose the event

Select the specific event that should fire the trigger. The available events depend on the integration. Examples:
  • Slack — new message in a channel, new direct message, new mention
  • Gmail — new email matching a filter (sender, subject, label)
  • Calendly — new booking created, booking cancelled, booking rescheduled
  • Linear — new issue created, issue assigned, issue status changed
Some events include additional filters. For example, a Slack trigger can be scoped to a specific channel, or a Gmail trigger can match on sender address or subject keywords.
5

Configure any filters

If the event supports filters, fill them in to narrow when the trigger fires. Filters prevent your script from running on every event of that type — only events matching your criteria will fire the trigger.
Use filters to keep your automation focused. A Gmail trigger scoped to emails from a specific sender is more reliable and cheaper to run than one that fires on every incoming message.
6

Choose an action

Under Action, choose what happens when the event fires:
  • Send Prompt — sends a message to the AI agent in a new session. Use this when you want the agent to decide how to respond, or when the task requires judgment based on the event content.
  • Run Script — runs a specific script directly. Use this for deterministic automations where you know exactly what should happen.
7

Create the trigger

Click Create Trigger. The trigger activates immediately and will fire the next time the matching event occurs in your connected tool.

​
What happens when the trigger fires

Each time the matching event occurs, Script.it creates a new session and runs the action you configured. The event data — the Slack message content, the Calendly booking details, the Gmail email body — is passed to the session as a payload, so your script can act on it. Sessions created by integration event triggers appear in your session history alongside manually started sessions and scheduled runs. If your action is Run Script, the session shows the execution results. If your action is Send Prompt, the agent responds to the prompt in the new session.
If your connected integration is revoked or expires, triggers that depend on it will stop firing. Script.it will show a warning on affected triggers in the Triggers tab. Reconnect the integration to resume normal operation.

​
Managing integration event triggers

From the Triggers tab on your script:
  • Pause / resume — use the toggle next to a trigger to temporarily disable it without deleting it. Paused triggers do not fire until you re-enable them.
  • Delete — open the trigger’s actions menu and select Delete. Deleting a trigger is permanent and immediately stops listening for the event.