Prospectio + n8n

Why wire it up

Most teams have the signal that should start an outreach campaign sitting in a different system to the one that sends it. Someone fills in a form, a company appears in an intent feed, a target account hires for a role, a trial signup goes cold. Each of those is a reason to reach out, and in most companies each of them gets noticed a week late by a human scrolling a dashboard.

n8n closes that gap. The signal fires, the prospect enters the right Prospectio campaign, the ICP filter checks they are worth messaging, and the sequence starts the same day.

What you can trigger

• Add a prospect to a specific campaign, with any custom fields you want available for personalisation
• Pause or resume a prospect’s sequence, for example when they open a support ticket or a deal moves stage
• Update a prospect’s details mid-sequence
• Remove a prospect entirely, which matters for suppression lists

What Prospectio sends out

• Connection request sent, and accepted
• Message or voice note delivered
• Reply received, with the text and the responder’s classification (interested, question, objection, not now, not interested)
• Meeting booked, with the time and the calendar link
• Prospect skipped by the ICP filter, with the reason, which is useful for auditing your targeting

Workflows worth building

Website visitor to campaign. A deanonymisation tool identifies a company, n8n looks up the right contact, Prospectio qualifies and starts a sequence.

Form fill to instant follow-up. Someone downloads something, n8n adds them to a nurture campaign that opens with a voice note rather than an autoresponder email.

Job ad signal to outreach. A monitoring tool spots a target account hiring for a role that signals need, and the campaign starts automatically.

Reply to Slack. Every positive reply posts into a channel so the team sees momentum, which does more for morale than a weekly report.

Meeting booked to CRM and calendar. Belt and braces alongside the native CRM sync.

Setting it up

There is no Prospectio node in n8n’s integration list yet, so you connect using the built-in HTTP Request node.

1. In Prospectio, go to Settings → Integrations and generate an API key
2. In n8n, build your trigger as normal, then add an HTTP Request node
3. Set the method to POST and the body content type to JSON
4. Add a header called X-API-KEY with your key
5. In the body, profileUrl is required, along with your campaignUuid and linkedinAccountUuid
6. Execute the node once with a single prospect before you activate the workflow

Your campaign UUID is on the campaigns page, under the three dots and View details. Your LinkedIn account UUID is on the accounts page, under the three dots and Copy.

n8n is open source and self-hostable, so this is the cheapest of the three to run at volume. There is no premium tier gating the HTTP node.

A caution

Automated triggers make it easy to accidentally message someone twice, or to message an existing customer. Keep a suppression list, and route everything through the ICP filter rather than straight into a sequence. The filter skipping a prospect is a feature, not an error in your automation.