How teams use SalesRobot with Tapistro
Teams running LinkedIn outreach through SalesRobot use Tapistro to feed their campaigns automatically. A Journey qualifies prospects using your signals, filters, and AI Agents, then adds them to a SalesRobot campaign so connection requests and messages go out without anyone building lists by hand.
SalesRobot is available in Tapistro as a Destination, so the handoff happens as the final step of a Journey. SalesRobot events also flow back into Tapistro as Signals, so a Journey can react to what happened in the campaign.
Before you connect
SalesRobot outreach runs through a LinkedIn account, so connect at least one LinkedIn account in SalesRobot first. Your API key is accepted without one, but campaigns and activation won't work in Tapistro until a LinkedIn account is connected on the SalesRobot side.
Connect SalesRobot
Go to Connections in Tapistro and select SalesRobot.
Paste your SalesRobot API key.
Save the connection.
Add prospects to a SalesRobot campaign from a Journey
Open your Journey and add a Destination step.
Select SalesRobot.
Pick the campaign from the dropdown. Tapistro fetches your campaign list live from SalesRobot, so you don't need to copy campaign IDs.
When the Journey runs, every person who reaches the Destination step is added to the selected SalesRobot campaign, and your LinkedIn sequence takes over from there.
How SalesRobot Signals show up in a Journey
Each SalesRobot event arrives in Tapistro as its own Signal, and the Signal carries the specific event type. The event type matches the value SalesRobot exposes in its Default Tag field, for example:
connected: the prospect accepted your connection request.replied: the prospect replied to your message.youreplied: you sent a reply to the prospect.
The event type is exposed as a top-level attribute on the Signal, so you can filter, branch, and score on it like any other Signal attribute. Open a Signal in the step report to see its full details.
Use the event type in a Journey to:
Route replied leads to a rep. Add a Conditional Branch step on the event type and send
repliedSignals down a path that alerts sales or writes to your CRM.Score a reply higher than a connection. Reference the event type in an AI Agent or an expression so
repliedadds more weight thanconnected.Trigger follow-up only on accepted connections. Add a Data Filter step that keeps
connectedSignals, then pass them to the next outreach step.