Authorize an app your team asked you to connect

When an agency builds an automation that touches one of your accounts, the workflow stays paused until you connect that account. This page walks you through the whole client side of that handoff: opening the request, authorizing each app on the provider's own consent screen, and confirming the workflow is no longer blocked.

You never type a password or an API key into TaskJuice or into anything the agency controls. Every app is connected through the provider's own sign-in and consent screen, and the agency never sees your password.

There are two ways a request reaches you, and which one you get depends on whether you already have a portal account:

• A branded link in an email, if you do not have a portal account. The email and the page it opens carry your agency's name and branding, not TaskJuice's.
• Your portal inbox, if you are a member of the workspace with a portal account. The request waits for you under Connections.

Both paths end the same way: each app opens its provider's consent screen, you approve, and the app flips to Connected. Pick the path that matches what you received below.

Before you start

You will need:

• The request itself, either the email your agency sent or access to your portal.
• Your own login for each app being connected (your Google account, your Slack workspace, and so on). You sign in at the provider, not at TaskJuice.

A single request can cover more than one app. You connect them one at a time, and the page tracks your progress as {x} of {y} connected.

Path A: Authorize from a branded link

Use this path if you received an email and do not have a portal login. You do not need to create an account.

1. Open the link in the email

   The email subject reads Action required: {agency name} needs you to connect ..., and the message is branded with your agency's name. It lists each app you have been asked to connect, the permissions each one needs, and any note the agency added explaining why. The email never contains a password, token, or key; it only carries a link.

   Click the single button in the email. It opens a page at a branded address, and the browser tab title reads Connect an app · {agency name}. No login is required.

2. Review the apps and progress

   The page heading reads {agency name} needs you to connect {N} apps. Below it, a progress line shows {fulfilled} of {total} connected with a progress bar, and a section titled Apps to connect lists one card per app.

   Each pending app shows an Awaiting authorisation badge and a Connect {app name} button. Apps you have already connected show a Connected badge.

3. Connect each app on its consent screen

   Click Connect {app name}. The button takes you straight to that provider's own consent screen, for example Google's or Slack's sign-in and permission prompt. Sign in with your account for that provider and approve the access the agency requested.

   You enter your credentials only at the provider. TaskJuice and the agency never see them.

4. Return and connect the rest

   After you approve, the provider sends you back to the branded page, the app's badge changes to Connected, and the {fulfilled} of {total} connected counter ticks up. Your session is remembered across the page, so you can connect the next app without verifying the link again.

   Repeat for every app until the counter reads {total} of {total} connected.

Path B: Authorize from your portal inbox

Use this path if you have a portal login for the workspace. The request waits for you inside the portal instead of arriving as an emailed link.

1. Sign in and open Connections

   Sign in to your portal and go to Connections (/portal/connections). At the top, an Outstanding connection requests panel lists what your team is waiting on, with a counter that reads {N} apps awaiting connection. Requests are grouped by the workflow they belong to.

   If you see "No outstanding connection requests", there is nothing waiting for you right now.

2. Open the workflow's requests

   Each workflow group has an Open button. Click it to go to that workflow's detail page (/portal/connections/workflows/{workflowId}), which shows {x} of {y} connected, a progress bar, and one row per app.

3. Connect each app on its consent screen

   Each unconnected app has a Connect {app name} button. Click it to go straight to that provider's consent screen. Sign in with your account for the provider and approve the access requested.

   As before, you enter credentials only at the provider, never in TaskJuice.

4. Watch each app flip to Connected

   After you approve, you return to the workflow detail page and the app's badge changes to Connected. The counter updates as you go. Connect every app in the group until each one shows Connected.

Confirm the workflow is unblocked

You have finished when every app in the request shows the Connected badge and the progress line reads {total} of {total} connected. At that point the agency's workflow has the credentials it was waiting on and can run.

You can confirm your connection any time from the Connections table on /portal/connections. Each app you connected appears there with a status:

• active: "Connected and working." This is what you want to see.
• pending: "Waiting for the first sync."
• error: "Reconnection needed." The connection needs attention.
• revoked: the connection was revoked and workflows depending on it will pause until you reconnect.

To check or fix a connection later, see Manage your connections.

What can go wrong

The link says "This link can't be opened." Branded links expire (7 days for an emailed link, 4 hours for a portal-inbox request, counted from when the agency sent it), can be used only once per app, and stop working as soon as the agency resends the request. For your security, the page shows the same message whether the link expired, was already used, or is otherwise invalid, so it will not say exactly which. The fix is the same in every case: ask the agency to send a fresh request. The new link replaces the old one.

You only see an API-key field, or want to paste a key instead. There is no key-pasting step in this flow. Client app authorization always runs through the provider's OAuth consent screen, so you sign in at the provider rather than entering a key. If an app a workflow needs cannot be connected this way, the request cannot be completed from your side; tell the agency so they can adjust the workflow.

A "Connect" button does nothing or returns an error. If the app on the request is not set up for sign-in based authorization, the button returns an error rather than opening a consent screen. This is an agency-side setup issue, not something you can fix from the link. Let the agency know which app failed.

You cannot cancel a request. Only the agency can cancel a request. From your side you can connect an app, and later refresh or revoke a connection you own. If a request arrived by mistake, ask the agency to cancel it.

Related

• Manage your connections - check connection health, refresh a credential, or revoke access.
• What clients see in the portal - how the portal is organized and what else lives there.
• Credential request statuses and expiry - exact request statuses, link expiry windows, and resend behavior.