A lead you find should reach not only the Telegrin Feed but also the place where your team works: Telegram, Slack, your CRM, Grinfi or your Claude routine. In a campaign this is the job of deliverers - the steps of the Delivery group in the Campaign pipeline. A campaign can have several at once.
Where leads can go
| Deliverer | What happens |
|---|---|
| Telegram bot | Lead cards arrive in your bot @telegrin_signals_bot. |
| Via Webhook | An event to your URL for every lead. |
| API connector | Your CRM's endpoint with field mapping. Your Claude routine is connected here too. |
| Slack | A lead card in your Slack channel. Each campaign can use its own channel. |
| Grinfi | Hands the lead over to your Grinfi account - LinkedIn only. Each campaign has its own Grinfi list; hand over By hand, from the card or Automatically on approval. |
ℹ️ Note: email is not a campaign deliverer. Lead emails are set once for the whole workspace: Settings → Notifications → Email (see "Notifications").
How to add a deliverer
- Open the campaign → Pipeline. Or Edit → the Agents step → AI agents.
- Press + where the step should go → the Delivery group → the deliverer you need.
- Pick a connection or create one right there - + New connection. Slack connects with the Go to Slack button.
- Press Add step.
The Telegram bot is not added to a campaign by itself: add it the same way, + → Delivery → Telegram bot, and subscribe to the bot @telegrin_signals_bot (see "Notifications").
Webhook and API connector steps have When to send in their settings: keep As in the connection or choose events - A lead appeared, We replied, The lead replied, The lead changed stage.
The main rule: your own deliverers or every connection
- The campaign has no deliverers, or only the Telegram bot. Every new lead also goes to every connection in the workspace: all webhooks and API connectors that accept new leads (including your Claude routine), and Slack - to the channel set in the connection.
- You added any other deliverer - a webhook, an API connector, Slack or Grinfi. From then on this campaign's leads go only to the deliverers you chose. The workspace's other connections no longer receive its leads.
⚠️ Important: add your own webhook to a campaign, for example, and Slack and Claude stop receiving its leads. If you need them, add them to this campaign too. Claude goes in as an API connector step: in the step settings, in the Connection field, pick your Claude routine. How to connect Claude is covered in "Telegrin → Claude: your Claude routine handles new leads".
Delivery order
Deliverers run in turn, top to bottom. The order is not cosmetic: it decides which system hears about a lead first.
- In the Pipeline a step lands exactly where you pressed +.
- On the campaign page, Agents tab, each deliverer has its number in the queue and up and down arrows - Deliver earlier / Deliver later. Numbers and arrows appear once there is more than one deliverer.
A new order applies to the next leads.
💡 Tip: put first the channel your team reacts to fastest - in lead generation, the speed of the first reply matters most.
⚠️ Important: if one deliverer is temporarily unavailable (say, a webhook does not respond), the others still get the lead - one channel failing does not stop delivery.
Related articles
- "Notifications"
- "Agents in a campaign"
- "Telegrin → Claude: your Claude routine handles new leads"
- "MCP and the public API"