Connectors, custom APIs and AI workflow generation

Connectors link your account to GitHub, Slack, Notion, Linear and Tavily with a token or a sign-in. Each app comes with a few actions that matter, such as creating a GitHub issue or posting to Slack, and their inputs are already described for the model.

We chose a short list done well over a long list done thinly. Tokens are checked with the app before they are saved, and a connection that stops working says so on the node before you run.

For everything else there are custom APIs. Give an API a base URL and choose how it signs in: no auth, bearer, API key, basic, digest, custom headers, OAuth 2.0 client credentials, OAuth 2.0 authorization code with PKCE, or AWS Signature v4. Save the endpoints you use, and every {placeholder} becomes an input on the API node.

PATCH /items/{item_id}
{ "title": "{title}" }

Tokens, keys and OAuth secrets are encrypted at rest and never sent to the browser. A workflow names the connection or API; the server adds the secret when it makes the call, and scrubs it from the response and the run record. A path can never leave the API's host, and private addresses are refused.

Generate with AI drafts a whole workflow from a description. The draft is validated like one you built yourself, repaired once if needed, and uses your connected apps and APIs by their real ids. You see it on a canvas before anything is created. The GitHub issue triage use case starts this way.