The industry-specific problem
Enterprise buyers ignore messages that describe their company without understanding its operating context. Reps need sourced reasons to contact an account, not another generic personalization token or a false claim about internal infrastructure.
Step-by-step workflow
- Read Salesforce accounts that have an assigned owner and are not in an active opportunity or suppression list.
- Query Clearbit API only through your available contracted product and store when each enrichment field was observed.
- Collect permitted public GitHub signals. Exclude secrets, personal repositories and unauthorized LinkedIn scraping.
- Use a currently supported Claude model to produce a hypothesis with source URLs, uncertainty and a proposed discovery question; Claude 3.5 Sonnet is a retired direct-API model.
- Create a Salesforce draft task for rep approval. Do not send solely because the model assigned a high fit score.
Visual workflow
Salesforce ownership → n8n enrichment → Clearbit + permitted GitHub evidence
→ Claude hypothesis + citations → evidence gate → rep-approved Salesforce task
Specific configuration example
This n8n Code-node fragment consumes a normalized, authenticated event from preceding integration steps. It demonstrates the decision boundary, not a complete API client. Fields are workflow-local mappings, not claimed vendor field names. Upstream credentials, schema validation, permissions, durable reservations and provider operations must be implemented separately. Numeric policy examples are illustrative, not Imperio service terms.
// n8n Code node: evidence-gated account hypothesis
const account = $json;
const cited = (account.signals ?? []).filter(s =>
s.public_url && s.observed_at && s.permission_verified);
return [{ json: {
salesforceAccountId: account.salesforce_account_id,
evidence: cited.map(s => ({ url: s.public_url, fact: s.observed_fact })),
draftAllowed: cited.length > 0 && !account.active_opportunity,
instruction: "Ask about the observed pattern; do not claim an internal outage."
} }];
Outcome to measure
Track rep acceptance of drafts, qualified replies and opportunities created per approved message. Illustrative planning: five minutes saved on research for 120 accounts frees ten hours; count a rejected unsupported draft as quality feedback, not a success.
Compared with manual work or other tools
Clay-style enrichment can assemble fields quickly; n8n is useful when evidence gating and Salesforce ownership need custom logic. Manual research remains preferable for a handful of strategic accounts requiring deep technical judgment.
Work with Imperio Automation
Ask Imperio to build a citation-first Salesforce research queue using your permitted enrichment sources.
Frequently asked questions
Can we scrape every employee LinkedIn post?
No. Establish an authorized access path and permitted purpose first.
Can it infer stack problems from commits?
It can frame a tentative question, not assert private operational facts.
What prevents two reps contacting the same account?
Use Salesforce ownership and an atomic campaign reservation before creating an outreach task.