Use Instantly's “Lead is marked as interested” event as the Zap trigger, then create or update a HubSpot contact by email and give a person responsibility for the next response. Do not send every reply to a deal stage. Negative replies, out-of-office messages and opt-outs need different handling.
Instantly publishes a specific Instantly-to-HubSpot Zapier recipe. This guide adds the operating decisions that the simple create-contact recipe leaves to your team: who classifies the reply, which existing contact gets updated, who follows up, how future cold sends stop, and how a failed Zap gets recovered. The provider instructions and Zapier's live Instantly–HubSpot action catalog were checked October 1, 2026; we have not run this automation in a private workspace.
Exact job: convert an interested lead status in Instantly into a usable HubSpot record and a human-owned follow-up. The broader HubSpot integration hub compares tools and connection types. Instantly also documents a native HubSpot connection for lead imports, SuperSearch exports and Automations. Choose the route your team can govern and monitor; do not run native and Zapier creation flows for the same event without a duplicate plan.
Decide what counts as an interested reply
The Zapier event is Lead is marked as interested, not Reply Received. This distinction matters. A reply can be a question, referral, rejection, automatic response or unsubscribe. The trigger fires when the lead gets the Interested category in Instantly, so the classification step is upstream of the Zap. Assign a person to correct false classifications and define whether the category is set by an operator or an approved automation in your workspace.
Jan showed the underlying CRM principle in a May 24, 2023 Pipedrive walkthrough: a positive reply became a contact and deal for sales work, while an unsubscribe went to suppression; he also described blocking existing CRM opportunities from further cold outreach. That is historical experience with Pipedrive, not a claim that he used this HubSpot Zap or the current Instantly connector. The durable lesson is to keep opportunity creation and opt-out handling separate.
| Instantly signal | CRM treatment | Sending treatment |
|---|---|---|
| Marked Interested | Match/create contact; assign an owner; review whether a deal is warranted | Stop the cold sequence and prevent a fresh import from restarting it. |
| Negative or Not interested | Record according to your retention policy; do not create a sales opportunity automatically | Apply your suppression policy. |
| Lead Unsubscribed or an opt-out by reply | Route to suppression and audit the result; never convert it into an Interested deal | Ensure it cannot be contacted by another active campaign. |
| Out of office or ambiguous reply | Keep for human review or a separate category route | Follow the relevant sequence and reply rules, not this Zap. |
Prerequisites and ownership
You need an Instantly workspace that can use its Zapier integration, a Zapier account with permission to publish the Zap, and a HubSpot account where the connected user can create or update contacts. Agree on one HubSpot owner or review queue, one contact email field, and one rule for deciding whether an interested reply deserves a deal. Keep the Instantly Zapier API key private; it is an integration credential, not a field to store on a lead.
Define the minimum mapping before opening the Zap editor:
| Field or decision | Recommended treatment |
|---|---|
| Lead email | Use the address from the event as the HubSpot contact email and matching key. Reject or review events without a usable address. |
| Name and company | Map only fields that are present and trustworthy in the event; do not replace better CRM values with blanks or guessed company names. |
| Source | Record that this was an Instantly interested handoff, plus campaign context if provided. |
| Reply context | Make the relevant reply visible to the owner through an approved note or task if your action and privacy policy support it. Instantly's trigger test exposes event details and reply text; exact available fields depend on the sample. |
| Owner and next action | Assign a real person or a monitored queue. A newly created contact with no next step is a lost reply in a different database. |
Step 1: Connect Instantly and select the right event
In Instantly, open Integrations and find the Zapier app. Instantly's Zapier integration guide describes both its classic and new interface and says to copy the Zapier API key there. In Zapier, create a Zap with Instantly → New Event, connect the account with that key, choose the intended campaign, and select Lead is marked as interested as the event type. Instantly says a blank campaign field applies the trigger to all campaigns. Use a named campaign when you are piloting one process; expand deliberately after the mapping and owner rules work.
Test the trigger with a controlled interested lead. Instantly's recipe says the event details can show the lead's reply text. Inspect the sample's actual field names and values in Zapier before mapping anything to HubSpot. If no real event is available, do not infer that a placeholder sample contains all production fields.
Step 2: Create or update the HubSpot contact by email
Instantly's simple recipe uses HubSpot → Create Contact. For an operating workflow that may see the same person in several campaigns, Zapier's HubSpot action catalog also lists Create or Update Contact, described as matching on email address. Use that action when it is available in your connected Zapier account and map the event's lead email to its required Contact Email input. This gives an existing contact a path to update instead of treating every interested event as a new person.
HubSpot's deduplication documentation says contacts are automatically matched by the Email property in several creation paths, but behavior varies by path, and secondary addresses or missing email can complicate identity. Do not assume a matching company domain identifies the same person. Avoid creating a company automatically from an email domain; HubSpot explicitly warns that companies created through API and third-party sync apps are not deduplicated by company domain in the same way as some UI and import paths.
An update action can overwrite existing CRM data. Map only fields this workflow owns, such as an agreed source label and latest Instantly campaign context. Preserve an existing owner, lifecycle stage, consent or suppression property unless your HubSpot administrator has approved an exact update rule. If multiple contacts or alternate emails make the identity ambiguous, hold the event for review instead of generating another record or overwriting a known one.
Step 3: Put the reply in a person's queue
Creating a contact is a database operation, not a sales handoff. Decide who should read the actual reply, answer it, and decide whether a deal should be created. HubSpot's connected user may be able to map an owner or add another action, but available fields and permissions vary by portal. A practical default is to map an agreed owner only when unassigned, then send ambiguous or unowned records to a monitored review queue. Preserve an existing CRM owner's responsibility.
Keep a small handoff record: Instantly campaign, lead address or CRM record ID, classification time, assigned owner, and disposition. The owner should be able to distinguish a new sales opportunity from a polite “not now.” If the team wants a deal, define its stage and create it only after that decision. A duplicate contact or deal is not an acceptable way to signal urgency.
Step 4: Confirm cold outreach will stop
Instantly's lead-status guidance says changing a lead away from the default Lead status stops that campaign sequence. The Zapier Interested event is a classification trigger; do not assume it alone proves the sequence has stopped. Check the lead's actual status and reply-stop settings, then apply the approved stop action if needed. For protection across imports and existing campaigns in the workspace, Instantly's Global Blocklist says its Blocklist tab is checked both on import and during ongoing campaigns. Decide whether an interested opportunity should be added there and who maintains that rule; do not assume this Zap's create/update action automatically changes the blocklist.
Treat opt-outs even more strictly. Instantly exposes a separate Lead Unsubscribed Zapier trigger, and its Blocklist settings describe an Unsubscribed leads automatic blocklist toggle. Review that setting and route opt-outs separately. A CRM contact record alone does not suppress future Instantly campaigns. The Instantly unsubscribe setup guide covers the link, header and suppression checks.
Test the handoff before publishing the Zap
Instantly's recipe says to test the trigger, verify the created contact in HubSpot, then publish. Use a small controlled test set that also checks the failure paths:
- New interested lead: classify a controlled reply as Interested; confirm exactly one HubSpot contact is created with source and owner or review queue.
- Existing contact: use an email already in HubSpot; confirm the intended contact is updated and its owner and protected fields remain intact.
- Unsubscribe or negative reply: confirm the interested Zap does not create a sales opportunity; verify the separate suppression process.
- Retry or duplicate event: replay a test if Zapier permits it; confirm the email match does not create a second contact or deal.
- Failure: deliberately inspect the Zap's task history and configure a named person to review failed runs. Reconcile any Instantly interested leads without a HubSpot owner rather than assuming every event arrived.
These are tests to perform in your accounts, not tests we claim to have run. Avoid using a real prospect or a production deal as a test fixture. Do not paste the API key or full private reply text into an issue ticket.
When this Zap is the wrong integration
Use the native Instantly HubSpot connection when its documented Automations meet your exact workflow and ownership needs without Zapier. Use a broader integration design if you must synchronize lifecycle stages both ways, reconcile historical replies, or propagate suppression across separate sending systems. The Interested-event Zap is a focused handoff, not a full CRM sync. Review the HubSpot integration hub for the wider tool landscape.
OutboundXYZ has a commercial relationship with Instantly. The connector steps above are documented provider behavior, while the owner, matching and suppression rules are our proposed operating design. Our Instantly.ai review covers the broader product decision.
Frequently asked questions
Can I use “Reply Received” instead of “Lead is marked as interested”?
You can build another workflow for every reply, but that is a different intake problem. Instantly's published HubSpot recipe uses Lead is marked as interested, which keeps negatives, auto-replies and opt-outs out of this contact handoff unless someone misclassifies them.
Will HubSpot automatically prevent duplicate contacts?
Do not rely on a general promise of deduplication. Zapier lists Create or Update Contact as an action based on email. Map a valid email, test an existing contact, and preserve a human review path for aliases and ambiguous records. HubSpot's matching rules differ among manual entry, forms, imports and integrations.
Does creating a HubSpot contact stop Instantly follow-ups?
No. The contact action changes HubSpot. Verify the lead's Instantly status and reply-stop settings separately. Instantly documents a nondefault lead status as a way to stop the current campaign sequence, while its workspace-wide blocklist is a separate control for existing and future campaign leads.
