---
title: "Route competitor buying signals with an AI agent | Letterdrop"
description: "Set up an agent that pulls Letterdrop's competitive-evaluation signals, filters them, combines them with your other signals and routes tasks to BDRs, AEs, customer success and ad audiences."
url: https://letterdrop.com/enablement/agents
updated: 2026-11-19
---

# How the signal gets worked

**Read this first**

**An agent works the signal, and people work the tasks it creates.** Every day your agent pulls the accounts Letterdrop flagged, filters them, combines them with your other signals and routes each one: BDRs get net-new accounts, AEs get accounts in their open deals, CS gets customers, and marketing's ad audiences update themselves.

Each person gets a task with the research done and the first drafts written, in the CRM or Slack they already use. This page is how to set that up.

Letterdrop signals + Your other signals: site visits, intent, job changes, CRM → your agent (filter, combine, route, draft) → tasks for:

-   [BDRs](https://letterdrop.com/enablement/reps): High, Medium and Low accounts with no open deal
-   [Ad audiences](https://letterdrop.com/enablement/marketing): InMail and demo ads, then awareness and retargeting
-   [Customer success](https://letterdrop.com/enablement/cs): Customers in an evaluation
-   [AEs](https://letterdrop.com/enablement/ae): Flagged contacts in their open opportunities

**The one rule**

**The agent can use the signal. The buyer never sees it.** Let the agent read which competitor an account is evaluating to pick the angle and the timing. Nothing it writes for a buyer names that competitor or hints that we know about the evaluation.

The agent drafts. A person reads and sends.

## What you need

-   **An agent that can make HTTP requests and run on a schedule.** Claude Code, Codex, a ChatGPT custom GPT with an action, or a workflow tool like n8n, Zapier or Clay all work.
-   **Your workspace API key.** In Letterdrop, go to Settings, then Integrations, then API Key. Store it as a secret named `LETTERDROP_API_KEY`. Never paste it into a chat. It gives full read access to your workspace, so RevOps owns it.
-   **Write access to where tasks land:** your CRM and Slack. Letterdrop’s API only reads.

## The five steps

-   **1\. Consume:** Receive the New Competitor Deal webhook as signals land, or pull the day's new accounts each morning.
-   **2\. Filter:** Drop accounts outside your buyer filters or on a do-not-contact list, and update open tasks instead of creating duplicates.
-   **3\. Combine:** Check site visits, form fills, third-party intent, job changes and CRM history. An account that shows up in Letterdrop and somewhere else goes to the top of its tier.
-   **4\. Route:** Customer goes to CS. Open opportunity goes to the AE. Everything else goes to a BDR. Every non-customer also goes into the ad audiences.
-   **5\. Write the task:** Account, why now, the people, CRM context, a due date and drafts, posted to the CRM and to the owner in Slack.

## Who gets what

The agent checks CRM state in this order, and the first match decides the owner.

| If the account… | It goes to | What they do |
| --- | --- | --- |
| **Is your customer** | The CS owner | Check account health, then defend the renewal or [introduce your product](https://letterdrop.com/enablement/cs#introduce) to the flagged contact if they’re on a team you don’t serve yet |
| **Has an open opportunity** | The AE on the deal | Ask about the flagged contacts who aren’t on the deal, and run [discovery on the other solutions](https://letterdrop.com/enablement/ae#discovery) they’re evaluating |
| **Anything else: High, Medium or Low** | A BDR: the owner if nobody has reached out, otherwise the queue | Reach out within 48 hours for High and Medium, within the week for Low. [The BDR play](https://letterdrop.com/enablement/reps) |
| **Every account except customers** | Marketing’s ad audiences | High, Medium and Low get InMail and demo ads. The full list gets awareness, webinar and event campaigns, then retargeting on Meta and Google. [The marketing play](https://letterdrop.com/enablement/marketing) |

Recently closed-lost accounts with no open opportunity go to a BDR, with the AE who lost the deal copied. AEs and CS owners hear about **any** signal on an account they own, even when someone else gets the task.

## The agent’s instructions

This is the whole playbook written for an agent: access, filtering, routing, what goes in each task, the drafts for each role and the rules. Give your agent the link, or paste it in as its standing instructions and change anything that doesn’t match how your team works.

**Link for your agent:** [letterdrop.com/enablement/letterdrop-agent.md](https://letterdrop.com/enablement/letterdrop-agent.md)

Full agent instructions: [https://letterdrop.com/enablement/letterdrop-agent.md](https://letterdrop.com/enablement/letterdrop-agent.md)

## Push instead of pull: the webhook

To start work the moment an account is flagged, add a **Send to Webhook** step to a Competitor Deal workflow in Letterdrop and choose payload version v2. Each new signal is POSTed to your agent’s URL with the contact, company, account and CRM context, using the same field names as the API, and an `api-key` header to verify it came from Letterdrop.

## What your agent can read

| Ask it for | Endpoint |
| --- | --- |
| Accounts in a competitive evaluation, filtered by priority, competitor, date, owner, CRM status or outreach status | `GET /accounts` |
| One company you already know, by domain | `GET /accounts/lookup?domain=acme.com` |
| The people with signals, one row per person | `GET /contacts` |
| The wider buying committee at an account | `GET /accounts/{account_id}/buying-committee` |
| Your outreach to the account and whether it led to a meeting | `GET /accounts/{account_id}/outreach` |
| CRM opportunities on the account | `GET /accounts/{account_id}/opportunities` |
| What the account’s job postings say about its tools and projects | `GET /accounts/{account_id}/job-postings` |
| Your buyer filters | `GET /buyer-filters` |
| Job changes at your target accounts | `GET /target-accounts/job-changes` |
| Meetings, deals, pipeline share and win rate on flagged accounts | `GET /analytics/...` |

The full list of filters and values is on the [filters page](https://docs.letterdrop.com/filters), and the full reference at [docs.letterdrop.com](https://docs.letterdrop.com).

## Limits worth knowing

-   **Read-only.** The API reads your Letterdrop workspace. Writing tasks to your CRM and Slack is your agent’s job.
-   **Daily data.** Signals are collected daily, so polling more often than every few minutes returns the same data. `meta.data_as_of` says when it was computed.
-   **Rate limits.** 10 requests a second and 600 a minute per workspace. Wait and retry on a 429.

## No agent yet?

Every play still works by hand. The role pages say what to do with a flagged account, and the [prompt library](https://letterdrop.com/enablement/agents/prompts) has prompts you can run one account at a time in any AI chat.
