Instantly integration

Email automation

Instantly is a cold-email outreach platform built around sending campaigns at scale across many warmed mailboxes. The NoClick Instantly node lets a workflow manage that whole machine: campaigns, leads and lead lists, the email accounts that do the sending, and the analytics that tell you what is working. It can also reply to threads and listen for events like a positive reply. Use it to automate the repetitive operations of running outbound sequences end to end.

What you can automate with Instantly

Instantly operations

Triggers1

Email Account6

Campaign10

Lead7

Lead List5

Email5

Analytics1

Templates using Instantly

Cold Email Reply Agent

Answers the interested replies to your cold campaigns within minutes, marks unsubscribes in the lead record, and hands every negative or complicated reply to a person. Cold campaigns die in the reply inbox. Someone says yes on Tuesday night, hears nothing until Thursday, and the interest is gone. This agent reads every reply as it lands, answers the interested ones and the simple questions using only what you told it about the offer, marks unsubscribes properly, and pings Slack with the leads worth a call. Anything negative or complicated goes straight to a person, because arguing with a prospect over email has never once worked. ## What people use it for - **Interested leads answered in minutes** - A reply that arrives at 22:00 gets a real answer and a next step before anyone opens the inbox. Speed is most of what closes a cold lead, and it costs nothing to be first. - **Unsubscribes handled properly** - Any wording that means stop contacting me, in any language, is marked in the lead record with no reply sent. That is list hygiene, and it is what keeps your sending domains healthy. - **Reps only see the yes pile** - Slack gets a line for the interested leads and the ones a human has to take, with the sentence that mattered quoted. Nobody scrolls a shared inbox looking for the two replies that were worth reading. - **It never argues with a prospect** - Negative, dismissive, or complicated replies get no answer at all, only a Slack line. On those threads the agent has exactly one job, which is to avoid making it worse. ## Before you fork **What do I need to connect?** An Instantly API key that can read emails, reply, read campaigns and update leads, plus a Slack channel for your reps. Then you write the offer context, meaning the pitch, the pricing you will put in writing and what the product does not do, and your reply policy. The staged replies in Setup show you the exact wording it would send before a real prospect sees anything. **What will it actually send on my behalf?** Three or four sentences, only to interested replies and to questions your offer context already answers, only once per thread, and only in reply to someone who wrote to us first. Everything to do with pricing you did not write down, security, contracts or integrations is left untouched and posted to Slack. It cannot start a new thread or email anyone who did not reply. **What does it cost to run?** One short run per reply received, not per email sent, so a campaign of 5,000 sends with a 4 percent reply rate is around 200 runs. Unsubscribes and negative replies are the cheapest runs of all, since they end after a lead update or a single Slack line.

78204 nodes

Questions

The Instantly node uses an API key, which you generate from Settings then Integrations inside your Instantly workspace. You enter the key into the node's credential field, and it then has access to your campaigns, leads, and email accounts.

Yes. The node has a Receive Webhook Events trigger that subscribes to events such as Reply Received, Email Opened, Link Clicked, Lead Interested, Lead Meeting Booked, and Lead Unsubscribed. A workflow can start automatically whenever one of those events fires.

You can create a single lead or use the bulk operation to add up to 1000 leads to a campaign or lead list in one call. There is also a move operation for shifting existing leads between campaigns or lists as their status changes.

The node can fetch analytics for a specific campaign, daily analytics across all campaigns, and warmup analytics for an individual email account. That covers both campaign performance, such as opens and replies, and the health of your sending mailboxes.

It can. The node lists, gets, creates, and deletes email accounts, and can pause or resume them. Pausing a struggling mailbox or adding a fresh one are common steps when keeping deliverability healthy across an outreach operation.