Sequencer Event Poller

Read the replies, bounces, unsubscribes, meetings booked, interest changes, and LinkedIn replies from your Instantly, Smartlead, HeyReach, and lemlist accounts in one place. Add your own API key for one or more of them, pick a time window, and get one flat row per event: who, which campaign, what happened, when, and the reply text where the vendor returns it. Schedule it daily with Only new events on and each run returns only what changed since the last one. Rows export to CSV or drop into a Clay table, a CRM import, or a reply routing step.

The actor only reads your account. It never creates, edits, pauses, or sends anything in a sequencer, and it never creates a campaign.

Features

• Four sequencers, one row layout. Instantly, Smartlead, HeyReach, and lemlist events land in the same columns, so one table holds every reply across tools.
• Your own API key. Each vendor is read on the key you supply, from your own account. Keys are used for the run only, never stored, and never written to a row or a log.
• Only new events. On a schedule, an event an earlier run returned is skipped and not charged.
• A run summary row, always. One free row per run with counts per vendor and event type and the status of each vendor (ok, partial, error, or skipped), so a refused key or a page limit is visible, not silent.
• Read only by construction. One function sends every request, and it refuses any call that is not a read. The only POST calls are the two search endpoints Instantly and HeyReach expose as POST to list records. The request_log in the run's RUN_SUMMARY record lists the method, endpoint, and status of every call, so you can check it yourself.
• Cost guards. Max pages per query, max events per run, and a max charge per run.

Which vendor reports which event

Instantly reports bounces and unsubscribes as a lead status, not as a dated event, so a bounce's time is the lead's last send and an unsubscribe's time is when the lead record last changed. HeyReach is read for LinkedIn replies only. A blank cell means the vendor's public API gives no read for that event, and the actor does not guess one.

Input

Number and yes or no fields are text fields, so a Clay column or any text value works: "25", "true", "no". A value that is not a whole number, or not true or false, is refused: the run ends successfully with one free row, row_status error and error_reason starting input_invalid: and naming the field. Only the start fee applies. List fields stay lists; in Clay, wrap a single column in a one item list.

With no key at all, the run returns one free run summary row with row_status skipped and a note saying no key was given.

Output

One row per event, plus one run summary row per run. Every row has the same columns.

Pricing

Pay per event. You pay for event rows and the run start. The run summary row is free, already delivered events are free, and a run with no key charges only the start.

Per 1,000 event rows: $8.00 on the free plan, $6.80 on Gold.

Free plan cap: 1.50 USD of evaluation a month, about 188 event rows. Any paid Apify plan removes the cap, and it resets on the 1st. The run stops before a charge that passes your maximum charge per run in Apify or your max_charge_usd.

Mamba Labs pays the platform costs of your run. The vendor API calls run on your own API key and your own vendor account, under that vendor's plan and rate limits. This actor adds no charge from any vendor.

Usage examples

Apify Console or API. Add your keys, set Look back to 24 hours, and schedule the actor daily. Read the dataset with GET https://api.apify.com/v2/datasets/{datasetId}/items.

{
  "lemlist_api_key": "YOUR_LEMLIST_API_KEY",
  "smartlead_api_key": "YOUR_SMARTLEAD_API_KEY",
  "since_hours": 24,
  "event_types": ["reply", "linkedin_reply", "bounce", "meeting_booked"],
  "only_new": true
}

Clay. Run the actor from a Clay HTTP column or the Apify integration and map the flat columns. Every input accepts strings.

MCP. The Mamba Labs MCP server @mambalabsdev/mcp-sequencer-event-poller exposes the tool poll_sequencer_events to Claude and other MCP clients. Vendor keys come from the server environment.

Error handling

Limitations

• The actor reads each vendor's public API as documented on 2026-10-21. A vendor that changes a field name can leave a column empty until the actor is updated.
• Instantly allows about 20 API requests a minute, so the actor waits about 3 seconds between Instantly requests. A large Instantly backfill takes minutes.
• Smartlead reply text, meeting, and interest events are not in its statistics endpoint, so Smartlead rows carry no message text and no meeting or interest events.
• HeyReach connection acceptances are not readable through its public API list endpoints, so they are not returned. lemlist reports them.
• Instantly bounce times are the lead's last send, and unsubscribe times are the lead record's last change; neither is a vendor event time.
• Live runs need your own vendor keys. The actor's tests use saved responses built from each vendor's public API documentation.

Mamba Labs actor suite

MCP servers for the suite are published under the npm scope @mambalabsdev.

Built by Mamba Labs.