DEV Community

chovy
chovy

Posted on Originally published at outreachgraph.com

OutreachGraph now runs the whole sequence: LinkedIn, branching, A/B angles, an inbox and your CRM

OutreachGraph started as the part most outreach tools skip: finding the thing a prospect said forty minutes ago that makes a message worth sending, and refusing to send anything the platform, the person or your own limits say it shouldn't.

Today it also runs the outreach after that. Six changes shipped to https://outreachgraph.com:

Sequences that branch

A cadence step can now wait on a condition: if connected, if not connected, if no reply, if they clicked. A LinkedIn connection request can hold the next step for up to a week while it waits for an accept. So "visit their profile, connect with a note, then DM if they accept or email if they don't" is one plan. A reply still ends it.

LinkedIn through your own session

Connection requests with a note, profile visits, follows, messages and comments now run through your own logged-in session. It stays off until the workspace owner accepts the risk, and it is paced and capped under LinkedIn's limits: 20 invitations a day and 100 a week per account. Without the opt-in, LinkedIn steps become hand-off cards you do yourself.

A/B test the angle, not a template

Give a step two, three or four reasons to write ("reference their talk", "ask who owns onboarding"). Each prospect is assigned one arm. Every message is still written from that prospect's own words and still has to pass the grounding checks. The plan page shows sends, clicks, opens and reply rate per arm.

Open tracking exists now too, and it is off by default. Apple Mail fetches every image on delivery, so an open is an upper bound and never raises a prospect's score.

One inbox, triaged

Replies are labelled interested, question, referral, not interested, out of office, bounce or unsubscribe. Rules go first and a model only labels what the rules can't. An unsubscribe suppresses the person immediately. Out-of-office notices no longer count as replies, so they don't stop a sequence. Interested and question replies get a drafted answer to approve. If you put a campaign on trusted automation and switch replies to autonomous, a confident answer to a direct question can go out unattended, and everything short of that stays a card.

More sending accounts, warmed up

Connect several mailboxes, LinkedIn sessions and X accounts. A conversation stays on the account that started it, a new account ramps its daily cap (email from 5 a day), and an account whose bounce rate passes 5% pauses itself.

Webhooks, Slack and your CRM

Signed webhooks for replies, clicks, approvals, sends, completed sequences and opt-outs, so Zapier, Make and n8n work out of the box. There is a Slack format, and replies and approvals are written to HubSpot or Pipedrive as notes.

Two fixes worth mentioning

Unsubscribe links and tracked links were answering 404 in production because the server only routed /api to the API. They work now. Autopilot sends were also missing the unsubscribe line and the List-Unsubscribe header. Every send path now shares one builder, so they can't drift apart again.

Free while in beta: https://outreachgraph.com

Top comments (0)