How to Integrate Intent Data Into Your CRM Without Breaking Your Workflow

Adding a new data source to your CRM sounds simple until you try it. Field mapping is wrong. Duplicates flood in. Your sales team ignores the new data because it does not fit their workflow. The integration project that was supposed to take a week takes a quarter, and by the end nobody is using it.

This guide covers the practical, step-by-step process to push intent signals into Salesforce, HubSpot, and Pipedrive without disrupting your existing workflows.

Before You Start: Define the Workflow First

The most common mistake is starting with the integration and then figuring out the workflow. Do it the other way around. Answer these questions first.

Who will act on the signals? SDRs, AEs, or account managers? The answer determines where signals land in your CRM.

What action should they take? Call within 24 hours? Send a specific email sequence? Add to a cadence? The action determines the automation rules.

How will you measure success? Signal-to-conversation rate? Signal-to-opportunity rate? Signal-to-close rate? The metric determines the reporting structure.

Once you have these answers, the CRM configuration is straightforward.

Salesforce Integration

Step 1: Create a custom object. Create "Intent Signal" as a custom object with fields: Signal Type (picklist), Signal Score (number), Filing Date (date), Source (text), Status (picklist: New, Contacted, Qualified, Closed).

Step 2: Configure the webhook. SIE sends a webhook for each new signal matching your filters. Use Salesforce Flow or a middleware tool (Zapier, Make) to receive the webhook and create a new Intent Signal record.

Step 3: Link to existing records. Match the signal to existing Account and Contact records using company name and domain. If no match, create a new Lead record linked to the signal.

Step 4: Build automation. Create a Flow that assigns new HOT signals to the appropriate rep, creates a Task with a 24-hour deadline, and sends a Slack notification to the sales channel.

Step 5: Build reporting. Create a report type that joins Intent Signals to Opportunities. Track conversion rate by signal type, territory, and rep.

HubSpot Integration

HubSpot's API makes this particularly clean. Create a custom object for signals, configure the webhook receiver using HubSpot's Operations Hub or a middleware, and build workflow automations that route signals to the right rep. HubSpot's native reporting handles signal-to-deal tracking without custom report types.

Pipedrive Integration

Pipedrive's webhook support and custom fields make integration straightforward. Create custom fields on the Deal object for signal metadata, use the webhook to create new deals in a dedicated pipeline stage ("Signal Received"), and build automation rules that move deals through stages based on rep activity.

Common Integration Pitfalls

Duplicate records. Always deduplicate against existing records before creating new ones. Match on domain and company name, not just email.

Signal fatigue. Do not flood your reps with 50 signals per day. Start with HOT signals only. Expand to WARM after the workflow is proven.

Missing feedback loop. If reps do not log outcomes (contacted, not interested, meeting booked, closed), you cannot optimize. Make the feedback fields mandatory.

Getting Started

See the API documentation -- full API documentation available at signup.

Frequently Asked Questions

How long does integration take? Most teams are live within 1-2 days using webhook + middleware. Direct API integration takes 1-2 weeks.

Do you support custom CRMs? Yes. Any system that can receive webhooks or call a REST API can integrate with SIE signal delivery.

What format is the webhook payload? JSON. Each payload includes signal type, score, filing date, source, and contact information (if revealed).

---

Ready to add intent signals to your CRM? See the API documentation