Skip to main content

Attention

Read Attention's recorded sales conversations, transcripts, scorecards and team data.

Connect it with: API key. Attention's own documentation: https://docs.attention.com/api-authentication.

What agents can do​

Connect Attention so the agents working your tasks can reach it. With it connected, they can:

  • List recorded conversations and read their transcripts, summaries and extracted fields.
  • Read scorecards and their results to review call quality.
  • Read users and teams to know who ran a call.
  • Pull call insights into a CRM update or a weekly summary.

Before you start​

  • An Attention account where you can create API keys (an organization-level key needs an admin).
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Attention​

Jaah connects to Attention with an API key, not with a sign-in button.

Connect with an API key​

Find each value first:

  • API key: Sign in at app.attention.tech, open Settings > API Keys, select Create API key, name it Jaah, choose organization level so agents can read every team's calls, and copy the key from the API Key Created window (it is shown once).

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Attention card.
  2. Name the secret and choose who can use it.
  3. Fill in API key.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Attention with an API key, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah calls Attention's API once (GET https://api.attention.tech/v2/users) with the stored values, and shows whether Attention accepted it, or which value Attention refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: api_key.

Tell the agent in your task description which secret to use, for example “use the Attention secret org/attention”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Attention once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Attention's side too, revoke or delete the key at Attention.

Limitations​

  • A user-level key reaches only that user's conversations; an organization-level key reaches every team's.
  • Attention rate-limits each key; ask your Attention account manager for a higher limit.
  • Transcripts can hold personal data from your calls; connect only for tasks that need them.
  • Agents can do only what the connected Attention account allows.

Troubleshooting​

Test says Attention rejected the API key (401)

The key was deleted or mistyped. Create a new one under Settings > API Keys and select Replace on the secret.

Test says Attention rejected the API key (403)

A user-level key may not list the organization's users. Create an organization-level key (an admin can) and replace the secret.

An agent finds no conversations

The key belongs to a user who recorded none. Use an organization-level key, or a key of the user whose calls agents should read.

Still stuck? Select Test and read the result: it names the value Attention refused and the status it answered.

FAQ​

How do I rotate the key?

Create a new key in Attention, select Replace on the secret, check that Test passes, then delete the old key in Attention.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Attention account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.