Connect an account to an app

You connect an app from inside the workflow builder, on the node that needs it. There is no separate "browse apps and click Connect" screen. When you add an app action or trigger to a workflow and open its panel, an authentication section appears where you select an existing connection or create a new one.

A connection is a stored credential to a third-party app. The connect dialog labels each connection an "account" in its buttons (for example, Connect New Account), but every connection you create is reusable: connect an app once, then point any node in the workspace at the same connection.

When to use this

Follow this page whenever a node shows that it needs an account, or when you want to add a fresh set of credentials for an app. The flow is the same for every app in the catalog, which is why per-app pages link here instead of repeating it.

The exact form depends on how the app authenticates:

• OAuth apps redirect you to the provider to authorize access, then hand a token back to TaskJuice. Examples: Slack, HubSpot, Google services.
• API-key apps ask you to paste a token or key you generate in the provider's own settings.
• Apps that need an extra field also ask for something like your account subdomain or region, in addition to OAuth or a key. Freshdesk, for example, asks for your Freshdesk subdomain.

You do not choose the auth type. The app's authentication method determines which form you see.

Open the connect panel

1. Add the app node to your workflow

   In the visual builder, add the app's action or trigger node and open its panel. A node that requires credentials shows an authentication section.

2. Open the account picker

   Open the authentication section to see existing connections for this app, scoped to the workspace you are in. The list is searchable with the placeholder Search accounts.... If you have not connected this app yet, you see No accounts available.

3. Start a new connection

   Select Connect New Account. If the app offers more than one authentication method, you first choose one under the heading Connect New Account with the prompt "Choose how you'd like to connect your {app} account." If the app has a single method, you go straight to its form.

Connect with OAuth

OAuth apps show the heading Connect via OAuth 2.0 with instructions from the provider, or the fallback line "You'll be redirected to {app} to authorize access to your account."

1. Fill any required fields

   If the app asks for an extra field such as a subdomain or region, enter it before continuing. These fields render above the authorize button.

2. Select Connect Account

   Select Connect Account. A popup window opens to the provider's consent screen. While it is open, the button reads Authorization in Progress....

3. Authorize on the provider

   Sign in to the provider if needed and approve the requested access. When you finish, the popup closes and the connection is created automatically.

Which OAuth app a connection uses

Every OAuth connection is made through an OAuth app registered with the provider, and the provider's consent screen shows that app's name. For each app, exactly one of these cases applies:

1. Your own app keys, turned on. The consent screen shows your agency's app.
2. Your own app keys, turned off. Nothing connects, even where TaskJuice's app is available. The node shows "{app} OAuth keys are turned off" until you turn the keys back on or delete them.
3. No keys of your own, and TaskJuice's app is available for that app. Connect works with no keys to add. On a node your agency connects, the line above the connection picker reads "Connects with TaskJuice's {app} app". The consent screen shows TaskJuice.
4. No keys of your own, and no TaskJuice app. The app cannot connect yet. The node shows Add OAuth keys to connect until you add your own app keys.

Your own app keys are optional wherever TaskJuice's app is available. Add them when you want the consent screen to carry your agency's name instead of TaskJuice's. They are required for apps where TaskJuice offers no app of its own.

1. Open the app's page

   App keys are managed by account admins. Open Apps in your account sidebar, then the app. Its Your own OAuth app section holds the app keys. The Use your own app keys or OAuth app keys link an account admin sees on the node opens the same section.

2. Add the keys

   Register an OAuth app with the provider using the redirect URI the form shows. Enter its client ID and client secret, tick the scopes your workflows need, and save. The Active checkbox in the same form turns the keys on and off.

On the Apps page, each OAuth app card shows which app connects it: Your app, TaskJuice app, or Your app (turned off). Each connection's details list the app it was made with under OAuth app.

What changes when you add, turn off or delete your keys. Only new connections are affected. A connection keeps using the OAuth app it was made with for as long as it exists; reconnect it to move it to the app that connects now.

• Adding your keys switches new connections to your app.
• Turning your keys off blocks new connections for that app, even where TaskJuice's app is available. The node shows "{app} OAuth keys are turned off". Tick Active again and save to turn them back on, or delete them to switch to TaskJuice's app where it is available.
• Deleting your keys switches new connections to TaskJuice's app where it is available. Where it is not, the app cannot connect again until you add keys.

Client connection requests follow the same order. When TaskJuice's app connects an app, your client signs in through it, and the request dialog tells you so: "Your client will see TaskJuice when they sign in". Add your own app keys so your client sees your agency's name on the consent screen instead.

Connect with an API key

API-key apps show the heading Connect with API Key with the provider's instructions, or the fallback "Enter your {app} API credentials to connect your account."

1. Name the connection

   Enter a Connection Name. This is required, and it is the name shown when you select this connection on workflow nodes. A clear name like Acme production helps when you have several accounts for the same app.

2. Enter the credentials

   Paste the key into the field the app asks for. Most apps use a single masked API Key field. Some apps ask for additional fields, such as a subdomain, alongside the key. Sensitive fields are masked with a show and hide toggle.

3. Select Connect Account

   Select Connect Account to save. The button reads Connecting... while it works.

You generate the key itself in the provider's own settings. The per-app reference page tells you where to find it: see Stripe or Twilio for examples.

Choose where the connection lives

Every connection has a scope. The default is Workspace.

• Workspace connections belong to one workspace, which usually maps to one client. Use this for a client's own accounts, such as their HubSpot, Stripe, or Twilio.
• Account connections are created once at the account level and shared across workspaces. Your agency manages them on the Apps page: open an app and add the account or API key there.

For most app connections you create in the builder, the scope is Workspace, and the connection is available only inside that workspace. To learn how scope decides who can use a credential, read Connections.

Verify it worked

After you connect, the node's account picker shows the new connection selected by name. A newly created connection starts in a pending state and moves to active once it is in use. The picker only lists connections compatible with the node and scoped to the current workspace, so seeing your connection there confirms it is usable.

To reuse it, open any other app node for the same app and select the same connection from the picker. You do not connect again. Re-running the connect flow for the same external account updates the existing connection instead of creating a duplicate, so you cannot accidentally end up with two copies of the same login.

Troubleshooting

The popup never opened. Your browser blocked it. Allow popups for the site and select Connect Account again.

The app node says no accounts are available. You have not connected this app in this workspace yet, or you are looking at a different workspace. Connections are workspace-scoped, so a connection made in one workspace does not appear in another. Connect the app in the workspace where the workflow lives.

A banner says a connection needs to be reauthorized. When an OAuth token can no longer be refreshed, TaskJuice raises a banner reading "A connection needs to be reauthorized" (or "{n} connections need to be reauthorized"). Follow the banner to reconnect. See Reconnect an integration.

The dialog says no methods are available. If you see "No accounts or authentication methods available for {app}. Please contact your administrator to configure OAuth providers," the app has no authentication method set up for your account. Contact your account administrator.

Related

• Connections explains scope and reuse in depth.
• Reconnect an integration resolves a connection that needs reauthorization.
• Request client credentials sends a client the connection request for their own account.