Let each user connect their own account

A user connection belongs to one user instead of the whole project. When that user triggers a workflow, an Integration step set to Current User (first connection) can use their account — for example, a booking workflow that puts the event on the booker's own Google Calendar.

How integrations work explains project and user connections.

Create a user connection

In the Anythink dashboard

The Anythink dashboard's Settings › Integrations page creates project connections only. Use the CLI, or build a "connect your account" page in your own app that calls the integrations API as the signed-in user with is_user_connection: true. The user's role needs anythink_integrations:read and anythink_integrations:create.

With the CLI

The connection belongs to the user signed in to the current CLI profile:

anythink integrations oauth connect google-calendar --user-connection --name "My calendar"
anythink integrations connect openai --user-connection --name "My OpenAI key"

integrations connect prompts for the API key without echoing it. OAuth providers need their OAuth client configured first — see Connect Google Calendar to create events from workflows.

With an AI assistant (MCP)

Connect my own Google Calendar to this project as a user connection, using the anythink CLI.

The assistant calls the cli tool with integrations oauth connect google-calendar --user-connection, and Google's consent screen opens in your browser. This needs the MCP server running locally in stdio mode.

Note: For API-key providers, run integrations connect in your own terminal. Through an assistant, the key would have to be passed in the command and would end up in your conversation.

Use it in a workflow

Set the Integration step's Credential Source to Current User (first connection). The step looks for an enabled connection visible to the user who triggered the job: their own user connection, or a project connection for the same provider.

The triggering user is whoever caused the event: the user whose API call created or updated the record, who pressed a workflow button, or who called the workflow's API route. Test Workflow runs as you.

Limit: If the project also has a connection for the same provider, Current User (first connection) may pick that one instead of the user's own — the order isn't guaranteed. Don't keep a project connection for a provider you use per user.

Limit: Timed workflows have no triggering user, so Current User (first connection) can only find project connections.

Verify

1. Run anythink integrations connections list --provider google-calendar while signed in as the user. Their connection's Scope column shows user <id>; project connections show tenant.
2. Trigger the workflow as that user and confirm it acted on their account — the event is on their calendar, not a shared one.

Each user sees their own connections and the project's, not other users'.

Variations

• One per provider. A user can hold one connection per provider in a project. To switch accounts, disconnect the old connection first; connecting again as the same user fails.
• Pick the connection explicitly. Store each user's connection ID on a record and use Specific Connection (by ID) with a template such as {{ $anythink.trigger.data.connection_id }}.

Next steps