Skip to content
SalesRobot logo
Close logo

SalesRobot → Close

SalesRobot + Close integration

When a SalesRobot prospect replies on social, the rep in Close should know first. OutboundSync logs each accepted connection, step, and reply on the Close Lead.

Get a demoRead the setup guide
BetaOne-way syncSocial

SalesRobot + Close at a glance

SalesRobot works with Close through OutboundSync. SalesRobot accepted and withdrawn connection requests, executed campaign steps, replies, and completed sequences are logged as activity on the matching Close Lead. The sync is one-way, SalesRobot into Close, and the OutboundSync team handles onboarding and the first test sync.

SalesRobot + Close integration facts
StatusBeta (Close is a one-way beta CRM)
ChannelsSocial
DirectionOne-way, SalesRobot → Close
Close recordsLeads
Block listsNot available for this pairing
SalesRobot planNeeds webhook access
SetupGuided: the OutboundSync team runs onboarding

Close teams often pair social prospecting with calling: warm the prospect up with SalesRobot, then call once they've accepted or replied. OutboundSync makes that timing visible by logging SalesRobot events on the Close Lead as they happen.

Completed sequences are a signal too. A Lead whose SalesRobot sequence finished without a reply is a candidate for a call or a different channel, and a Smart View can collect them for another touch.

What syncs from SalesRobot to Close

Every event below arrives in near-real time and lands on the matched Close record. Pick the ones you want per source.

SalesRobot events OutboundSync syncs to Close
EventChannelWhere it lands in Close
Connection request acceptedSocialActivity on the Close Lead
Connection request withdrawnSocialActivity on the Close Lead
Campaign step executedSocialActivity on the Close Lead
Reply receivedSocialActivity on the Close Lead
Sequence completeSocialActivity on the Close Lead

Event names come from the SalesRobot webhooks OutboundSync receives. Close is a one-way beta, so exact event coverage is confirmed during onboarding. See the SalesRobot event reference.

What teams do with SalesRobot + Close

  • Call after acceptance

    A Smart View of freshly accepted SalesRobot connections becomes a warm call list.

  • Catch replies fast

    SalesRobot replies land on the Close Lead so reps respond while the thread is live.

  • Rescue finished sequences

    Filter Leads with completed sequences and no reply for another touch.

Ways to connect SalesRobot and Close

The options teams weigh before they commit a production sync.

Ways to connect SalesRobot and Close, compared
OptionWhat it doesTrade-off
Zapier, Make, or n8nCompare integration platformsCatch SalesRobot webhooks and write each event to Close with a workflow you build.Every event type, retry, and field change is a workflow you maintain, billed per task or step.
Custom buildBuild vs buyWrite your own service against the SalesRobot and Close APIs.You own matching, deduplication, API limits, and every upstream schema change.
OutboundSyncPre-built social activity sync into Close Leads.One-way beta with guided onboarding. Lighter configuration than HubSpot or Salesforce today.

How to set up SalesRobot + Close

  1. Step 1: Connect Close

    Authorize OutboundSync from the Close App Marketplace. The OutboundSync team adds Close as a Connected Account with you.

  2. Step 2: Connect SalesRobot

    The OutboundSync team creates your SalesRobot source with you and points SalesRobot's webhooks at it.

  3. Step 3: Create the Close source

    Select SalesRobot when you create the Close source, and confirm how contacts are matched.

  4. Step 4: Send a test event

    Trigger one SalesRobot event and confirm it on a real Close Lead.

  5. Step 5: Go live

    Launch with the OutboundSync team watching the first production events in Close.

Close beta guideSalesRobot setup guide

Plan requirements

SalesRobot plan

Needs webhook access

OutboundSync receives SalesRobot activity through webhooks. Confirm your SalesRobot plan includes webhook access, or ask us to check during setup.

Close

Close is a one-way beta. There is no Close plan gate on our side; onboarding runs with the OutboundSync team.

Trusted by outbound teams

Redis
Windsurf
Gainsight
Sendoso
Crescendo
Tapcheck

SalesRobot + Close FAQ

  • What SalesRobot activity does OutboundSync sync to Close?
    Connection request accepted, connection request withdrawn, campaign step executed, reply received, and sequence complete.
  • Which Close records does it write to?
    OutboundSync matches or creates Close Leads. SalesRobot events land as activity on the Close Lead. See the Close beta guide for details.
  • Can I see which SalesRobot step a Close Lead reached?
    Yes. Each executed campaign step is logged as activity on the Lead, so you can see how far the prospect got before replying or finishing.
  • Is the integration one-way or two-way?
    One-way. Activity flows from SalesRobot into Close, and nothing is written back to SalesRobot.
  • Can I use Close records as a block list?
    Not today. Block lists come from HubSpot lists or Salesforce reports. The Close beta syncs activity in only.
  • Do I need admin access to set it up?
    A Close admin authorizes OutboundSync from the Close App Marketplace during guided onboarding.
  • Which SalesRobot plan do I need?
    OutboundSync receives SalesRobot activity through webhooks. Confirm your SalesRobot plan includes webhook access, or ask us to check during setup.
  • How is SalesRobot + Close priced?
    Beta access is scoped with the OutboundSync team during onboarding. Billing follows the same model as every plan: sent messages per month. Replies, opens, clicks, and lead-category updates are not billed. See the pricing page.
  • Can I do this with Zapier, Make, or n8n?
    Yes, for lightweight automation. Zapier, Make, and n8n are good for prototypes and simple routing, but they need ongoing maintenance and bill by task or step. OutboundSync is pre-built for outbound CRM sync, keeps searchable event logs beyond 30 days, and prices by outbound volume.
  • What breaks first when this scales?
    Data quality and reliability break first: duplicate events, retries, out-of-order webhooks, and bursts during big sends. OutboundSync handles idempotency, timing buffers, and queue recovery, and flags suspicious or mismapped payloads instead of writing them.

SalesRobot resources

Tutorials, case studies, and updates related to SalesRobot.

See SalesRobot activity in Close

A quick walkthrough with your own stack. Setup takes minutes, with no long-term contract.

Get a demo