Skip to main content
Connecting an integration takes a few clicks. You authorize a tool from your account settings, then scripts can use it without storing credentials in the script itself. Script.it supports OAuth for tools like Gmail and Slack, API key authorization for tools like Airtable, and custom REST API definitions for tools outside the built-in catalog.

​
Connecting an integration

1

Open Settings → Integrations

In Script.it, click Settings in the sidebar, then select Integrations. This page shows your connected tools, shared integrations, and a search field for the full catalog.
2

Find the tool you want to connect

Type the name of the tool in the search field. The catalog includes 600+ apps — scroll the results or refine your search until you find the one you need.
3

Click Connect

Click Connect next to the tool. Script.it opens the authorization flow for that integration.
  • OAuth tools (Gmail, Slack, Google Sheets, Notion, and most others) — you’ll be redirected to the tool’s own sign-in page to grant access. Sign in and approve the requested permissions.
  • API key tools (Airtable, and others that use token-based access) — a dialog prompts you to paste your API key or personal access token.
4

Complete the authorization

Follow the prompts until the authorization is complete. For OAuth tools, you’ll be redirected back to Script.it automatically once you approve access. For API key tools, click Save after entering your credentials.
5

Confirm the connection

The tool now appears in your connected integrations list with a Connected badge. It is immediately available to your scripts.
The AI agent can also prompt you to connect a missing integration during a session. If you describe an automation that requires a tool you haven’t connected yet, the agent will pause and ask you to authorize it before continuing. You can complete the connection without leaving the chat.

​
Sharing a connection with a workspace

When you share a connection, workspace members can call the upstream API using your connected account. This is useful for team-owned tools such as a shared Slack bot, a reporting mailbox, or a company CRM account.
1

Open the connected integration

Go to Settings → Integrations and find the connected account you want to share.
2

Open sharing settings

Use the sharing control on the integration row. It shows which workspaces already have access.
3

Choose a workspace

Select the workspace that should be able to use the connection. The share is scoped to that workspace. You can share the same connection with more than one workspace.
4

Confirm the trust boundary

Confirm that members of the target workspace should be able to use the connection under your upstream account.
A shared connection delegates use of your upstream account. Every Editor and Reader in the workspace can call it, and provider logs may show requests as you.

​
Sharing a custom integration type

Custom integration types are different from connections. A type is the API recipe: base URL, auth mode, OAuth client details, schema, and display metadata. It does not share member credentials. When you share a custom integration type with a workspace, members see it in their integration catalog and can connect their own accounts through it. Scripts can reference the same integration type, while each run uses the runner’s own credentials. This works well for internal APIs, customer-specific APIs, or partner APIs where every teammate should connect their own account.

​
Disconnecting an integration

To remove a tool’s access to your account:
  1. Go to Settings → Integrations.
  2. Find the connected tool.
  3. Click the ··· menu next to it and select Disconnect.
Disconnecting an integration immediately revokes Script.it’s access to that connected account. Any scripts that use that connection will fail if they try to call it after disconnection. To restore access, connect the integration again. If the connection was shared with one or more workspaces, disconnecting it removes the underlying account for everyone. If you only want to stop one workspace from using it, remove the workspace share instead.

​
Authorization types

Different tools use different authorization methods. Script.it handles both transparently, but it’s helpful to know which to expect:
MethodHow it worksExamples
OAuthYou sign in to the tool directly and grant permission. Tokens are managed automatically.Gmail, Slack, Google Sheets, Notion, HubSpot, Linear, Jira
API keyYou paste a key or token from the tool’s developer settings.Airtable, and other tools with personal access tokens
For OAuth integrations, Script.it stores only the access token — your credentials are never visible to Script.it. For API key integrations, your key is encrypted at rest.

​
Custom APIs

If the API you need is not in the built-in catalog, create a custom integration. Custom integrations support API keys, bearer tokens, basic auth, custom headers, and OAuth2 flows.