Connecting your accounts
Connect Slack, GitHub, and other providers — OAuth or API key, from Settings or straight from a step's config — and how the AI picks which connection to use.
Connected-app steps and BYO-key AI need a connection — a stored credential MadMax uses on your behalf. There are two ways in, and they end in the same place.
From Settings
Settings → connectors is the gallery: every provider as a card, filterable by connected / available / coming soon. Click one to connect:
Connected cards show the connection label and age; "coming soon" cards aren't wired yet.
- OAuth providers (Slack, GitHub, Google, …) — one button: Connect with MadMax. The provider's own consent screen opens in a popup; you never paste a token, and MadMax stores only the grant it's given.
- API-key providers — a short form: an optional label ("Production OpenAI"), the key field(s), and which workspace owns it.
From the canvas
Every step with a connection field has + Add new at the bottom of its picker — the same connect flow in a modal, without leaving the canvas. When the step already knows its provider, you go straight to that provider's form.
Private or shared
Every connection has a visibility pill:
- private (the default) — only you can see and use it.
- shared — any member of the workspace can bind it in their steps.
Click the pill to flip it. Secrets are never shown either way — sharing shares the ability to use, not the credential itself.
Which connection does the AI pick?
When Max builds a workflow that needs a provider, the rule is mechanical and deliberately conservative:
- 0 matching connections — the build pauses with a needs a connection card; you connect, it continues.
- exactly 1 — auto-wired, and the card notes which one it used.
- 2 or more — Max never guesses. You get a "which account should max use?" choice per step.
A connection's optional defaults (visible on its Settings panel) are applied at auto-wire time — handy for things like a default Slack channel.