Setting Up Integrations
Connect external services with Forge — connectors, credentials, and triggers, set up and tested in one conversation.
Connecting a service in Studio involves three pieces: a credential (how to authenticate), a connector (what to call), and often a trigger (when to react). Forge knows this chain and walks it in order — you only handle the part that shouldn't go through a chat: the secret itself.
Connecting a service
Start with the credential, and create it by hand in Application > Integrations > Credentials (see Credentials). Then hand the rest to Forge, referring to the credential by name:
You: I've added a credential "Telegram Bot Prod". Connect the bot
on it so workflows can send messages.
Forge: Connector created on "Telegram Bot Prod" and tested — the
bot responded. Want me to wire it into a workflow?Forge creates the connector on top of your credential and tests the connection — so you find out immediately whether the setup works, not later when a workflow fails at midnight. Creating the connector is a medium risk approval.
Don't paste secrets into the chat
Forge will accept an API key or token typed into the chat and create the credential from it — but we strongly recommend against it. Everything you send is kept in the conversation history, so the secret stays visible there. Create credentials manually in Studio and refer to them by name instead.
Connecting your own API
For internal or custom services, Forge can read the API's actual structure:
You: Connect our inventory service — REST, at
https://api.internal.example.com, key auth.
Forge: Connector created and tested. I inspected the API schema:
it exposes /items, /stock, and /reservations. Which of these
should the order workflow use for the stock check?The same works for GraphQL endpoints — Forge introspects the schema and builds correct queries instead of guessing field names.
Forge inspects a service's schema through its connector, so the connector comes first. If you ask about an API that isn't connected yet, Forge will offer to create the connector before exploring it.
Reacting to events: triggers
To make things happen automatically, ask for the behavior:
You: When a customer messages the Telegram bot, run the support
workflow.Forge creates the trigger and subscribes the workflow to it. Note the approval text for this one: subscribing starts firing on real events. From the moment you approve, actual messages will start the workflow — this is the step where your integration goes live, so it always asks first.
Scheduled runs are just another trigger: "run the cleanup workflow every night at 2am".
Changing and removing integrations
Rotating a token is best done by hand in the credential settings — for the same reason as above: the new secret shouldn't pass through the chat. Deleting a credential or connector through Forge is a high risk approval, and the card will warn you: any workflow that uses it will break.
If a connection misbehaves, start with a check: "test the CRM connector" — no approval needed, and Forge reports what the service answered.