Connectors
Services a wizard works in for the person who runs it – built in, from the registry or over MCP.
Settings → Connectors lists the services the space’s wizards can work in. A wizard uses a connector with the account of the person who runs it: they connect their account during the run, on a page that asks for it. Each space has its own connectors. In a team on engenty.ai, the owner and the admins add and remove them. In the cloud, a space you publish from your computer shows its connectors without letting you change them: you change them on your computer.
Built in
| Service | The person signs in with |
|---|---|
| Gmail, Google Drive, Google Calendar, Google Contacts | Google (OAuth) |
| Outlook, OneDrive | Microsoft (OAuth) |
| Slack | Slack (OAuth) |
| GitHub | GitHub (OAuth) |
| HubSpot | A token they enter |
| S3 | Keys they enter |
The OAuth services need an OAuth client of your own, which you enter in the settings file of engenty wizards. A built-in connector shows up in the list once it can be connected, so a service without its client doesn’t appear. Google is the exception on your computer: without a Google client of your own, Gmail, Drive, Calendar and Contacts connect through your engenty account, which holds the client. Connecting then asks you to sign in to the account first (Settings → Account).
| Service | Settings |
|---|---|
GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET | |
| Microsoft | MICROSOFT_OAUTH_CLIENT_ID, MICROSOFT_OAUTH_CLIENT_SECRET |
| Slack | SLACK_OAUTH_CLIENT_ID, SLACK_OAUTH_CLIENT_SECRET |
| GitHub | GITHUB_OAUTH_CLIENT_ID, GITHUB_OAUTH_CLIENT_SECRET |
- Give each client the redirect address
<your address>/api/connect/callback.CONNECT_REDIRECT_URLsets a different one. - For Google, enable the APIs you use and add their scopes to the consent screen.
- A connection asks only for what the wizard’s actions need.
You find the settings file under Command line.
From the registry
Any other service comes from the integrations.sh registry:
- Search for the service, for example Notion or Stripe.
- “Import” adds it from its API description or its MCP server.
- Its actions appear, marked as “reads”, “changes” or “deletes”. Some services list them only once an account is connected. “Reload actions” asks the service again.
If a service needs an OAuth client of your own, it says so. Remove it and import it again with “Your own OAuth client”.
The editor’s chat does the same while it builds a wizard: ask it to work with a service, and it finds and imports the connector. An AI app connected to engenty wizards can do this too.
What a wizard may do
A wizard names the actions it uses. Without a list, it uses only the actions that read. During a run:
| The action | What happens |
|---|---|
| Reads | It runs without asking, unless the wizard says to ask |
| Changes something | The person allows each call, or chooses “Allow for the rest of this run”. A wizard can let it run without asking |
| Deletes | The person allows it like a change. A wizard can never let it run without asking |
The person’s mailbox
A wizard can ask for the person’s mailbox and read it: search emails, read them and keep attachments. It never writes. The person chooses how to connect:
| Way | What engenty wizards needs |
|---|---|
| Any mailbox over IMAP | Nothing |
| “Gmail” button | The Google client, with the Gmail API enabled and the scope gmail.readonly. On your computer without one, your engenty account |
| “Outlook” button | The Microsoft client, with the delegated permission Mail.Read |
Connected systems
This section also holds “Connected systems”: MCP servers of your own, each with a name, its MCP URL and, if the server wants one, an authorization header. AI steps read from and write to these systems only where you allow the server on the step.
This is the other direction of AI apps: here engenty calls other servers, there your AI app calls engenty.
Goose, the help assistant
The chat at the bottom of every studio page. Goose knows engenty wizards, sees the page you are on, shows you where things are and fills in the space.
Models and account
What runs the AI in your wizards – an AI client on your computer, your own API keys, a local model or credits.