Connections
Many workflow blocks reach out to other services — Slack, Gmail, Google Sheets, an AI provider, and so on. Connections is where you set up the accounts and API keys those blocks use. Secrets are stored securely and only used when a workflow runs — they're never shown back to you.
The Connections Tab
Open Workflows → Connections. Connections are grouped into two shelves:
- Connected accounts — services you sign into (OAuth), like Google and Microsoft
- API credentials — services you connect with a key or token, like OpenAI, Slack, or Notion

Connecting an Account (Sign-in)
- Click Connect account
- Choose the provider — Google or Microsoft
- Sign in through the popup and approve access
When it succeeds you'll see Account connected.
:::info Coming soon More sign-in providers (such as Slack and GitHub) are on the way — they appear with a Soon badge for now. :::
Adding an API Key
- Click Add connection
- Search for the service (e.g. Slack, Notion, OpenAI)
- Give the connection a Name (e.g. "My OpenAI key")
- Paste the key or token
- Click Create
For services that support it, Arketic runs a quick test and tells you the result — for example Credential verified.
Health & Testing
Each connection shows a health state:
| State | Meaning |
|---|---|
| Connected | Working |
| Invalid | The key or token was rejected — re-enter it |
| Action needed | Expired — reconnect to refresh |
| Not tested | Hasn't been checked yet |
| Can't auto-verify | This service can't be tested automatically |
Use Test now to re-check a key connection, or Reconnect to refresh an account.
Using a Connection in a Block
When you configure a block that needs a service, pick the connection from its credential dropdown. If you don't have one yet, you can add it right there. For sign-in–based services, connect the account first under Connections.
Managing a Connection
Click a connection to open its details:
- See its type, when it was added, and when it was last checked
- Re-enter a key or Reconnect an account when needed
- Delete or Disconnect it (blocks that used it will stop working)
Tips
- Name connections clearly — you may have more than one per service
- Watch for Action needed — reconnect before a run depends on it
- Least access — give keys only the permissions the workflow needs