Connectors

A connector joins your apps to a service you already have: Stripe for payments, OpenAI for AI, Resend for email, Google Sheets for data. You connect it once, on your account, and every app you choose can use it. There are more than sixty, from payments and shops to CRMs, calendars, AI and design tools.

Every app already has a database, sign-in and emails of its own, with nothing to connect: that is Cloud, at the top of the list, built in and always on. Connectors are for what comes from outside.

Where to find them

• On the dashboard or in the editor: +, then Connectors, to choose which ones this app may use.
• Manage connectors, at the foot of that window, opens the Connectors page itself, where services are connected. It opens over the editor or the dashboard, so you keep your place.
• On the Connectors page, the list on the left filters the tiles by All, Enabled, Custom connectors, MCP servers and by kind of service, and the search box finds a service by name.
• + at the top right adds one that is not on the list: describe it yourself with Custom connector, or ask us with Request a connector. MCP server is there too, for the AI that builds your apps rather than for the apps.
• In the editor, Manage, then Integrations, shows what this app can use. See Integrations.

Connect a service

Open the service on the Connectors page. Each one says what your app can do with it, what it does not do where that matters, and how much your apps used it in the last 30 days. There are two ways in: signing in to the service, or pasting the keys it gives you. The Connectors page shows the one each service has. Some have both, and then the page says Sign in with the service, or add your own keys instead.

With a button. Stripe, Notion, Google Sheets, Airtable, Slack, Discord, Calendly, Google Calendar, Microsoft 365, HubSpot, Pipedrive, Zoho CRM, Zoho Books, Salesforce, Linear, Asana, Atlassian (Jira and Confluence), Figma, Canva, GitHub and GitLab connect by signing in to the service and coming back. You never see or copy a key. For Stripe the button is Set up Stripe: see Online stores. Salesforce asks your admin to install Setherion's package once before the first sign-in.

With keys. For the others, paste the keys the service gives you under Credentials. Where do I find these? opens the right page of the service, and each box has a hint saying exactly which key it wants. Test connection tries them before you rely on them, and Connect keeps them. Once connected, Update changes them and Remove takes them off. If Connect is grey, a box is empty or you have not yet ticked the line that says you understand the service's terms: Take me there jumps to it.

A connected service shows a green dot on its tile, and Enabled beside its name. Before the first connection, each service says in plain words what it means for you, and you tick that you understood. A badge sums it up: Billed by the service when it charges you for use, for example Billed by Supabase, Handles real money for payments and shops, and No usage charges for the rest.

The next step after Connect

Right after you connect a service on its page, a card says Stripe is connected. Next: use it in this app, or build an app with it when you came from the dashboard. Its button, Use in this app or Build an app with it, writes a starter request in the chat for you, like "Use Stripe in this app: online payments, subscriptions and invoices", and puts the service on the app's list. The request waits in the message box. Nothing is built or spent until you press Send. You can close the card, and it does not come back on later visits. Design and code services, like Figma and GitHub, have no such card, because they are read while an app is built rather than used by it.

What a service does not do

Where a service has an obvious limit, its page says so in a grey note, with a button to the connectors that do the job instead. PayPal is the example: each button buys one item, there is no cart, and your app is not told when someone pays, so the note points to Stripe and Paddle.

Choose which apps use it

Connecting a service does not put it in every app. In the app, open +, then Connectors, tick the ones this app may use, and press Done. Anything you leave off stays out of the app's code and its keys. A service that is not connected yet has Connect beside it, which takes you to its page.

Then ask for what it should do, in the chat:

You do not have to tick first. If your message names a service the app cannot reach yet, a bar above the message box says This needs Stripe and offers three answers: Use it here when it is already connected, Connect with a key or the service's own sign-in, right there, or Build without it. Without it, the app says the feature is not set up rather than pretending it works.

Permissions

Some services list what your apps may do with them, under Permissions on their page once they are connected. Each line has two buttons: the tick allows it, the crossed circle switches it off.

• A change is saved as you press it, and applies at once to every app that uses the connection, published ones included.
• An app that tries something switched off gets an error that says so, and where to turn it back on. New builds are told, and leave it out.
• The service still grants your key or sign-in everything it was given. These limits are Setherion's, kept on top of it.
• Removing the connection turns everything back on.

Shopify is different. Your apps call it straight from the page with its Storefront token, which is public by design, so its limits are set in Shopify: open Sales channels, then Headless, then your storefront, press Manage beside Storefront API, and edit Permissions. Its page on Setherion shows the same steps.

Supabase, Firebase, Google Maps and Cloudinary are the same: your apps call them straight from the page, so their limits are set in each service, and their page on Setherion says where.

Every other service says in one sentence under Permissions everything your apps can do with it, such as only sending emails, or only reading your products. Canva, Figma, GitHub and GitLab say that your apps never use them: only you do, from the editor.

HubSpot

HubSpot brings your CRM into your apps: contacts, companies, deals and tickets. There are two ways to connect it.

• Connect with HubSpot: sign in at HubSpot, choose the account and approve. Until HubSpot has finished reviewing Setherion, its screen warns that the app is not verified yet and asks you to type "I accept the risk" to go on.
• A service key: in HubSpot, open Development, then Keys, then Service keys, and create one with read and write for contacts, companies, deals and tickets. Paste it under Credentials. HubSpot's keys start with pat-.

Who may use it in a published app:

• Anyone: a form on your site may add a contact or a ticket.
• Your team only: reading the CRM and changing anything in it. Mark the accounts that are your team in Manage, then Cloud, then Users. See Working as a team.

To stop apps changing your deals while they still read them, switch off Change for deals under Permissions.

Your own Supabase

Supabase is optional: every app already has a backend. Connect it when you want an app's data in a Supabase project of your own.

• Credentials: the project's address and its anon key, which is public by design. The service role key is optional.
• Connect Supabase account, under Creating the tables, lets Setherion create the tables an app needs in your project, from Manage, then Cloud, each time you press the button there. You sign in at Supabase and approve it. The permission stays on Setherion's servers and is never handed to the apps you publish. Without it, the tables are still there for you to copy and paste into Supabase yourself.

To move an app that already has data to your own Supabase, see Advanced settings.

What there is

Every connector, grouped the way the pages that describe them are. Each page has one dropdown per service: what it is for, which keys it wants and where to find them, what to ask for, its switches, and its limits.

For a service that is not on the list, describe it yourself: see Custom connectors. For a single key one app needs, Secrets is enough.

Who can use a connection

Your keys never reach a visitor, so a published app calls a service through Setherion, and Setherion decides what is allowed.

• Only the paths an app needs. An app that sends email can send, and cannot reach your account, your keys or your domains. A shop front reads products and cannot read orders or customers.
• The sender and the account are fixed. An app cannot pick a different From address, phone number, calendar or list than the one you saved.
• Your team and your visitors are different. For a CRM, a visitor's form may leave a lead and your team alone may read or change anything. Mark your team in Manage, then Cloud, then Users. Each connector's page says which of its actions are public.
• Anything that reaches a person or costs money is rate limited. Email, texts, chat messages, sign-ups and payments are limited to about ten calls an hour for each visitor. Reads of your own data allow far more. An app that goes over is told to try again later.
• A daily and a monthly fuse. One app can make a few thousand calls to services a day, and a published app's calls use integration credits.

In a team workspace

On Business, Settings, then Connector settings, gives a team workspace two choices. Only the owner or an admin can change the first, and only the owner can lend.

• Which connectors the workspace's apps may use. A connector that is not allowed is left out of every build, puts no key into a published app, and every call to it is refused.
• Lending the owner's connections. A member's app can use the owner's connection to a service the member has not connected themselves. The keys stay on our servers and never reach the member. The provider bills the owner's account for those calls, and they count against the creator's integration credits.

Payments, shops and databases are never lent: their accounts, payouts and data belong to whoever connected them. See Workspaces.

Custom connectors and MCP servers

For a service that is not on the list, describe it yourself: see Custom connectors. To give the AI that builds your apps its own tools, add an MCP server.

Good to know

• A call a published app makes to a connected service uses one integration credit. See Plans and credits. You see what each app spent under Usage.
• Services that bill you for use, like Resend, Twilio or OpenAI, bill your own account, at their prices. Set a spending limit there: Setherion limits how fast an app may call, which stops abuse, but cannot cap what you spend.
• When an app calls a service that is not connected, Manage, then Integrations, says so, with Add the key.
• Disconnecting a service stops every app that uses it from reaching it, at once.