Skip to main content

Loops

Send transactional email and manage contacts and events in Loops.

Connect it with: API key. Loops's own documentation: https://loops.so/docs/api-reference/intro.

What agents can do​

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

  • Send a transactional email from a template published in Loops.
  • Create or update a contact and its properties.
  • Send an event that starts a Loops automation, for example a signup or a finished trial.
  • Add contacts to or remove them from mailing lists.

Before you start​

  • A Loops account and team.
  • For transactional email, a template published under Transactional, whose ID the agent needs.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Loops​

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

Connect with an API key​

Find each value first:

  • API key: Loops > Settings > API (app.loops.so/settings?page=api) > Generate key, then copy the key.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Loops 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 Loops with an API key, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah calls Loops's API once (GET https://app.loops.so/api/v1/api-key) with the stored values, and shows who it answered as, or which value Loops 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 Loops secret org/loops”.

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 Loops 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 Loops's side too, revoke or delete the key at Loops.

Limitations​

  • The key reaches the whole Loops team; Loops has no per-key permissions.
  • Loops limits each team to about 10 requests per second.
  • Agents can do only what the connected Loops account allows.

Troubleshooting​

Test says Loops rejected the API key (401)

The key was revoked or mistyped. Generate a new key under Settings > API and select Replace on the secret.

Sending fails with a transactional ID not found

Publish the template under Transactional in Loops and give the agent its transactional ID, shown on the template's Publish step.

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

FAQ​

Can agents send marketing campaigns?

No. Loops' API sends transactional email and events; campaigns are sent from the Loops editor.

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 Loops account?

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