Use multiple accounts from the same service

Name each account

Call the provider’s account helper at module scope with a stable binding name, then pass each reference to the trigger or action that should use it:

automations/route-support-email.automation.ts

import { automation } from "automate.ax"
import { gmail, googleAccount } from "automate.ax/gmail"

const supportGoogle = googleAccount("support")
const operationsGoogle = googleAccount("operations")

export default automation("Route support email", () => {
  const email = gmail.onNewEmail({ account: supportGoogle })

  gmail.sendEmail.usingAccount(operationsGoogle)({
    subject: email.subject.transform(
      (subject) => `New support email: ${subject ?? "(no subject)"}`,
    ),
    text: "A new message arrived in the support mailbox.",
    to: "operations@your-company.example",
  })
})

The names support and operations identify deployment bindings, not provider account IDs. Account helpers prevent passing a Google binding to an action for another service.

Connect each account

Deploy the project:

bunx automate.ax deploy

Automate.ax detects the permissions for each service and binding. For an unsatisfied binding, the command-line tool asks you to select an eligible account, connect one, or reauthorize one for broader permissions.

Only binding names appear in automation code and deployment metadata. Provider credentials stay private.

Keep one identity across calls

Use the same binding name wherever work should use the same provider identity. For example, Gmail and Google Sheets share the Google service, so googleAccount("operations") identifies the same Google binding across both product subpaths.

Omitting the action’s account options selects the default binding. A single-service action also accepts a binding string, while an account reference reuses one identity across calls.

Trigger account selection must be static because Automate.ax configures event sources during deployment. Actions resolve their selected account when they execute.

To change which connected account satisfies a binding, assign its replacement on the next deployment. A successful deployment records the new choice without code changes.

Start

Concepts

Guides

Use multiple accounts from the same service

Name each account

Connect each account

Keep one identity across calls

​Name each account

​Connect each account

​Keep one identity across calls

Name each account

Connect each account

Keep one identity across calls