Build a Social Intent Pipeline with Buska + n8n (No Code)

Why n8n for social listening automation

You could use Zapier or Make for this workflow, and they'd work fine. But n8n has three advantages for social listening pipelines specifically. First, it's free to self-host, which matters when you're processing hundreds of webhook events per day. Zapier charges per task, and at scale those costs add up fast.

Second, n8n handles complex branching logic better than most no-code tools. Social signals need different treatment based on platform, intent score, author type, and keyword match. n8n's visual workflow builder makes it easy to create conditional paths without getting lost in nested if/then/else configurations.

Third, n8n has a built-in HTTP Request node that can call any API, which means you can integrate enrichment services, CRMs, and outreach tools that don't have native n8n integrations. For social listening workflows where you're chaining 5-6 different services together, this flexibility is critical.

The pipeline architecture

Before we build, here's what the complete pipeline looks like. Understanding the full picture makes each step clearer.

1. Webhook trigger: n8n receives the Buska webhook payload when a new mention is detected.
2. Score filter: An IF node checks the intent score and routes high-intent mentions forward. Low-score mentions get logged but not processed further.
3. Enrichment: An HTTP Request node calls an enrichment API (Clay, Clearbit, or Apollo) to find the author's email, company, and role.
4. ICP check: Another IF node checks whether the enriched lead matches your ideal customer profile.
5. CRM push: Qualified leads get created as contacts in HubSpot, Salesforce, or your CRM of choice.
6. Slack notification: The team gets alerted in Slack with the mention text, enrichment data, and a link to the CRM record.
7. Outreach enrollment (optional): High-scoring leads get added to a Lemlist or Instantly campaign automatically.

Step 1: Create the webhook trigger

In n8n, create a new workflow and add a Webhook node as the trigger. Set the HTTP Method to POST. n8n will generate a unique webhook URL. Copy this URL.

Now go to your Buska dashboard. Navigate to Settings, then Integrations, then Webhooks. Paste the n8n webhook URL and save. To test the connection, trigger a test event from Buska. You should see the payload appear in n8n's webhook node. The payload includes fields like mention_text, platform, author_username, post_url, intent_score, and keyword_matched.

Step 2: Filter by intent score

Add an IF node after the webhook trigger. Set the condition to check whether the intent_score field is greater than or equal to your threshold. I recommend starting at 60. Mentions scoring below 60 are usually brand mentions, general conversations, or low-quality posts that aren't worth processing further.

The IF node has two outputs: True and False. Connect the True output to your enrichment node (we'll build that next). Connect the False output to a "No Operation" node or a logging node if you want to keep a record of filtered-out mentions for analysis later.

Step 3: Enrich the lead

Add an HTTP Request node connected to the True output of your IF node. This node will call an enrichment API to turn the social signal into a full lead profile. Here's how to set it up with a few common enrichment services.

Using Clay's API: Set the method to POST, the URL to Clay's enrichment endpoint, and pass the author_username and platform as parameters. Clay will return the person's email, company, title, and LinkedIn URL.

Using Apollo: Set the method to POST, the URL to Apollo's people/match endpoint, and pass whatever identifying information you have (username, name, company). Apollo returns similar enrichment data.

Using Clearbit: Set the method to GET, the URL to Clearbit's person API with the email or social handle as a parameter. Clearbit returns company and person data.

If the enrichment call fails (the person can't be found), add an error handling branch that either skips the lead or stores it for manual review. Not every social signal will be enrichable, and that's fine. Focus on the ones that are.

Step 4: Check ICP fit

Add another IF node after the enrichment step. This checks whether the enriched lead matches your ideal customer profile. Typical ICP checks include:

• Company size: employee count within your target range (e.g., 10-500)
• Industry: matches one of your target industries
• Role seniority: the person is a decision-maker or influencer (VP, Director, Head of, Founder, etc.)
• Geography: the company is in a region you serve

In n8n, you can chain multiple conditions in a single IF node using AND logic. Leads that pass all conditions flow to the CRM push step. Leads that fail get routed to a different path (maybe a lower-priority channel or a nurture sequence instead of direct sales outreach).

Step 5: Push to your CRM

n8n has native nodes for HubSpot, Salesforce, Pipedrive, and several other CRMs. Add the appropriate CRM node and map the enriched fields to contact properties.

For HubSpot: use the "Create/Update Contact" action. Map email, first name, last name, company, job title, and your custom properties (social signal text, platform, intent score, post URL). Set the lead source to "Social Listening - Buska" so you can track attribution later.

Add a Set node before the CRM node to format and clean the data. For example, capitalize names, standardize company names, and calculate a composite score from the intent score and ICP match. Clean data in the CRM saves your sales team time later.

Step 6: Notify the team

Add a Slack node after the CRM push. Send a formatted message to your #social-leads channel that includes the mention text, the enriched company and person info, the intent score, and a direct link to both the original social post and the new CRM record.

This closes the loop. Your team sees the alert, can check the CRM record for full context, and respond on-platform or via email, all within minutes of the original mention being posted.

Step 7 (optional): Auto-enroll in outreach

For leads that score exceptionally high (both intent and ICP fit), you can add an additional branch that automatically enrolls them in an outreach campaign. Use n8n's HTTP Request node to call the Lemlist or Instantly API, passing the enriched lead data and the original signal text as a personalization variable.

Be thoughtful here. Automatic outreach should only trigger for the highest-quality signals. Set the threshold high (intent score above 80 AND strong ICP match). For everything else, let your team review and respond manually. Automation should accelerate your best opportunities, not spam marginal ones.

Hosting and reliability

If you self-host n8n, make sure your instance is running reliably and has enough resources to handle webhook events in real time. A basic VPS (2 CPU, 4GB RAM) handles most social listening volumes comfortably. Enable n8n's built-in execution logging so you can debug failed runs. Set up error notification (n8n can send you an email or Slack message when a workflow fails) so you catch issues before they pile up.

Alternatively, use n8n Cloud if you don't want to manage infrastructure. The pricing is competitive with Zapier and Make, especially for high-volume workflows.