Enrich new Discourse members then notify in Slack for high value leads
Configured with Clearbit, Filter, Slack, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Routing
- Integration
- Trigger
- Messaging
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Filter out common personal emails | Routing | Filter | See node parameters |
| No clearbit enrichment available | Routing | No Op | See node parameters |
| Enrich user with Clearbit | Integration | Clearbit | person |
| Get company info | Integration | Clearbit | See node parameters |
| Filter for high value leads | Routing | Filter | See node parameters |
| On new Discourse user | Trigger | Webhook | See node parameters |
| Post message in Channel | Messaging | Slack | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
clearbitApislackApi
Workflow notes
Filter out common personal emails
Saves on Enrichment credits
Sticky Note1
👈 Optional If the workflow ends here, the email wasn't found in Clearbit. Consider checking with another enrichment service or sending a Slack message for manual verification.
Sticky Note2
Optional 👇 Change filter criteria here to determine what "high value" means for you
Enrich user with Clearbit
Clearbit returns a 404 error (and in n8n empty output payload) when email is not found
Enrich new Discourse members then notify in Slack for high value leads
Enrich new Discourse members then notify in Slack for high value leads
🎥 Watch set up video (~2min)
Sticky Note
1. ☝️ Set up On new Discourse user Trigger and Webhook in Discourse
Open https://{Your discourse root domain}/admin/api/web_hooks/new/edit to create a new Webhook in Discourse. See detailed instructions in 🎥 set up video
Sticky Note4
2. 👇 Set up Post message in Channel node
Change Channel parameter to your channel like #sales or #townsquare
Enrich new Discourse members then notify in Slack for high value leads
Enrich new Discourse members then notify in Slack for high value leads
Purpose and structure
This folder contains the Enrich new Discourse members then notify in Slack for high value leads workflow. Its executable nodes use clearbit, filter, noOp, slack, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
On new Discourse user
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Webhook/0414_Webhook_Filter_Create_Webhook.json MIT; preserve source notices.