Connect Sales Tools
Help the user design and implement integrations between sales tools — from choosing the right integration method through trigger/action design, field mapping, and error handling. This skill covers webhooks, Zapier/Make, native integrations, and custom API pipelines.
Step 1 — Gather context
Ask the user:
-
What are you connecting?
- Source tool (where the event happens): Mailshake, Apollo, Salesloft, Smartlead, Lemlist, Yesware, Groove.cm, Mixmax, Reply.io, Woodpecker, HubSpot, Salesforce, Qwilr, other
- Destination tool (where the action should happen): Salesforce, HubSpot, Slack, Pipedrive, other
- Is this one-way or bidirectional?
-
What should trigger the integration?
- A) Email reply received
- B) New lead captured
- C) Meeting booked
- D) Deal stage changed
- E) Contact created/updated
- F) Sequence/cadence completed
- G) Form submission
- H) Custom event — describe it
-
What should happen when triggered?
- A) Create a record (contact, task, deal, activity)
- B) Update a record (field change, stage change, owner change)
- C) Send a notification (Slack, email, SMS)
- D) Enroll in a sequence/cadence
- E) Multiple actions — describe
-
What's your technical comfort level?
- A) No-code — Zapier, Make, native integrations only
- B) Low-code — comfortable with basic API calls, can follow docs
- C) Code — can build custom integrations with API + webhooks
-
What's your current stack? (list all sales/marketing/CRM tools in use)
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
Step 2 — Integration architecture
Choose the right integration method based on complexity and technical requirements.
Decision matrix
| Method | Best for | Technical skill | Cost | Reliability |
|---|
| Native integration | CRM sync, built-in connectors | None | Free (included) | High |
| Zapier / Make | Multi-step workflows, no-code | Low | $20-100/mo | High |
| Webhooks + handler | Real-time events, custom logic | Medium | Free-low | Medium-high |
| Custom API pipeline | Complex transformations, high volume | High | Varies | Depends on implementation |
Native integrations — always check first
Before building anything custom, check if a native integration exists:
| Tool pair | Native integration? | What it does |
|---|
| Mailshake → Salesforce | Yes | Push leads, sync activity |
| Mailshake → HubSpot | Yes | Push leads, sync activity |
| Mailshake → Pipedrive | Yes | Push leads |
| Apollo → Salesforce | Yes (bi-directional) | Full contact/account/deal sync |
| Apollo → HubSpot | Yes (bi-directional) | Full contact/account/deal sync |
| Salesloft → Salesforce | Yes (bi-directional) | Contact/account/activity sync |
| Salesloft → HubSpot | Yes | Activity sync |
| Smartlead → HubSpot | Yes (native) | Push leads, sync activity |
| Smartlead → Salesforce | Via OutboundSync (third-party) | Lead and activity sync |
| Smartlead → Clay | Yes (native) | Enrichment pipeline |
| Lemlist → HubSpot | Yes (native) | Push leads, sync activity |
| Lemlist → Salesforce | Yes (native, 2-way) | Lead and activity sync |
| Lemlist → Pipedrive | Yes (native) | Push leads |
| Yesware → Salesforce | Yes (Enterprise plan, bi-directional) | Email/calendar/activity sync, inbox sidebar |
| Yesware → Gmail | Yes (Chrome extension) | Email tracking, templates, campaigns |
| Yesware → Outlook | Yes (add-in) | Email tracking, templates, campaigns |
| Yesware → Zoom | Yes (native) | Auto-generate meeting links in scheduler |
| Yesware → LinkedIn | Yes (native) | Prospect insights from inbox |
| Mixmax → Salesforce | Yes (Growth+CRM plan) | Inbox sidebar, auto-create leads, activity sync, advanced rules |
| Mixmax → HubSpot | Yes (Growth plan) | Activity sync, list import, sidebar |
| Mixmax → Slack | Yes (native) | Real-time tracking notifications |
| Mixmax → LinkedIn Sales Navigator | Yes (native) | InMail and connection requests in sequences |
| Mixmax → Zoom | Yes (native) | Auto-generate meeting links |
| Reply.io → Salesforce | Yes (native, bi-directional) | Contact/lead sync, email/call/task activity, status sync, custom workflows |
| Reply.io → HubSpot | Yes (native, bi-directional) | Contact sync (auto-sync every 2h), email/call/task activity, status sync, field mappings |
| Reply.io → Pipedrive | Yes (native) | Contact sync, activity logging |
| Woodpecker → HubSpot | Yes (native, with API add-on) | Contact sync, activity logging, deal stage triggers |
| Woodpecker → Pipedrive | Yes (native) | Contact sync, activity logging |
| Woodpecker → Salesforce | Via Zapier | Contact sync, activity logging |
| Woodpecker → Clay | Yes (native) | Enrichment pipeline |
| Woodpecker → Calendly | Yes (native) | Meeting booking from campaigns |
| Qwilr → Salesforce | Yes | Proposal/quote sync — see |
| Qwilr → HubSpot | Yes | Proposal/quote sync — see |
Rule: If a native integration covers your use case, use it. Native integrations handle auth, retry, and error handling automatically. Only go custom when native doesn't support your specific trigger or action.
Step 3 — Common integration patterns
Lead/reply → CRM record + notification
Trigger: Reply received in Mailshake/Apollo/Salesloft
Actions:
- Create or update contact in CRM
- Create activity/task on the contact record
- Send Slack notification to rep
Implementation options:
- Zapier: Trigger = Mailshake "Reply Received" → Actions = Salesforce "Create Task" + Slack "Send Message"
- Webhook: Mailshake push event (Reply) → your endpoint → Salesforce API + Slack API
- Native: Mailshake-Salesforce integration (auto-syncs replies as activities)
Meeting booked → CRM + sequence exit
Trigger: Meeting booked (Calendly, Chili Piper, or CRM scheduler)
Actions:
- Update contact status/stage in CRM
- Remove from active sequence/cadence
- Create deal/opportunity
- Notify AE
CRM status change → sequence enrollment
Trigger: Lead status changes to "MQL" in CRM
Actions:
- Enroll contact in outbound sequence (Apollo, Salesloft, Mailshake)
- Assign to appropriate rep based on routing rules
Implementation options:
- Zapier/Make (no-code): HubSpot "Lifecycle Stage Change" trigger → Apollo "Add Contact to Sequence" action. Easiest setup, handles auth automatically.
- CRM webhook + custom API (low-code): HubSpot workflow triggers webhook → your endpoint calls Apollo
POST /contacts/add_to_emailer_campaign
- Native CRM workflow (if supported): Some CRM-to-engagement-tool integrations support enrollment triggers natively — check Settings > Integrations before building custom.
Error handling for sequence enrollment:
- Duplicate contact: Check if contact already exists in the engagement tool before creating — use "Find or Create" logic
- Already enrolled: The API may reject enrollment if the contact is active in another sequence — handle gracefully (log, skip, or queue for later)
- Sequence capacity / enrollment limits: Sequences may have max enrollment caps or daily add limits. Monitor the API response for limit errors and implement a retry queue for overflow.
- Re-qualification: If a lead was previously disqualified and re-enters MQL, decide whether to re-enroll or skip (prevent spamming the same contact)
Deal stage change → stakeholder notification
Trigger: Deal moves to "Proposal Sent" or "Negotiation" in CRM
Actions:
- Notify relevant stakeholders in Slack
- Create follow-up task for rep
- Trigger proposal creation in Qwilr (see )
Multi-tool activity sync
Trigger: Any activity logged in engagement tool (email sent, call made, meeting held)
Action: Sync activity to CRM as a completed task/activity
Key considerations:
- Define sync direction (one-way vs bidirectional)
- Map fields between tools (Salesloft "Call" → Salesforce "Task" with type "Call")
- Handle duplicates (check if activity already exists before creating)
Step 4 — Platform webhook reference
Mailshake webhooks
- Setup: API endpoint with and
- Events: Sent, Open, Click, Reply, LeadCatcher, Bounce, Unsubscribe
- Payload: JSON with event type, recipientID, campaignID, timestamp, event-specific data
- Full reference: See →
references/mailshake-api-reference.md
Apollo webhooks
- Setup: Settings > Integrations > Webhooks
- Events: Contact created, contact updated, sequence enrollment, sequence completion, email bounced
- Note: Apollo's webhook support is more limited than Mailshake's. For complex automations, use the REST API with polling.
Salesloft webhooks
- Setup: Settings > Integrations > Webhooks (admin only)
- Events: Person created/updated, cadence step completed, email bounced, call logged
- Note: Salesloft also offers a robust REST API for building custom integrations
Smartlead webhooks
- Setup: API endpoint with and
- Events: LEAD_REPLIED, LEAD_INTERESTED, LEAD_UNSUBSCRIBED, EMAIL_SENT, EMAIL_OPENED, EMAIL_CLICKED, EMAIL_BOUNCED
- Payload: JSON with event_type, timestamp, and data object (lead_id, campaign_id, email, event-specific fields)
- Full reference: See →
references/smartlead-api-reference.md
Lemlist webhooks
- Setup: API endpoint with and event configuration
- Events: Reply, open, click, bounce, unsubscribe, lead interested, lead not interested
- Rate limits: 20 requests per 2 seconds on all API endpoints
- Full reference: See →
references/lemlist-api-reference.md
Groove.cm webhooks
- Setup: GrooveSell product settings > Webhooks
- Events: Sale, Refund, Failed Rebill, Cancellation
- Payload: JSON with event type, product, customer, and transaction data
- Note: Groove.cm has no public REST API. For integrations beyond webhooks, use Zapier (triggers/actions for GrooveMail and GrooveSell).
- Full reference: See
Yesware integrations
- No public API: Yesware does not offer a public REST API. No webhook endpoints, no developer docs.
- Integration methods: Native connectors only — Salesforce (Enterprise plan), Gmail, Outlook, Zoom, LinkedIn, Clari, DocSend
- Zapier: Limited Zapier support — check Zapier for available triggers/actions (may be community-built, not official)
- For custom integrations: No programmatic access. If you need Yesware data in other tools, the Salesforce integration (Enterprise plan) is the best bridge — sync Yesware activity to Salesforce, then integrate Salesforce with other tools.
- Workaround: For teams needing API access, consider Salesloft, Apollo, or Mailshake which all offer full REST APIs.
Reply.io webhooks
- Setup: API endpoint or via Settings > Integrations > Webhooks in dashboard
- Events: Contact replied, email sent, email opened, email clicked, email bounced, contact status changed, task created (specific event types available via )
- Delivery management: API endpoints for managing webhook delivery, retries, and failures
- API versions: V3 (beta) has full webhook management; V1/V2 have basic webhook support
- Full reference: See →
references/reply-api-reference.md
Woodpecker webhooks
- Setup: API endpoint or via Settings > Integrations > Webhooks in dashboard
- Events: Prospect replied, email sent, email opened, email clicked, email bounced, prospect status changed, prospect interested (specific events via webhook management endpoints)
- API access: Requires API & integrations add-on (€20/mo)
- Rate limits: Same as main API — 1 concurrent request, queue of 6
- Full reference: See →
references/woodpecker-api-reference.md
Mixmax rules (webhooks)
- Setup: Dashboard at app.mixmax.com/dashboard/rules or API with trigger and actions
- Trigger types: IF/THEN rules on email events (open, click, reply), Salesforce object changes (new/updated opportunities, accounts, custom objects), date fields, lead owner changes
- Action types: Webhook call, Salesforce record update, sequence enrollment, task creation, Slack notification
- Advanced rules: Growth+CRM plan — trigger on Salesforce objects, use complex logic (AND/OR conditions)
- API: , ,
POST/GET /rules/:id/actions
- Note: Mixmax rules are more of an automation engine than simple webhooks — they combine triggers and actions with conditional logic. For simple webhook forwarding, create a rule with a webhook action.
Qwilr webhooks
- Full reference: See for Qwilr-specific webhook events and CRM integrations
Step 5 — Data sync best practices
Define source of truth
Before building any bidirectional sync, decide which tool is the source of truth for each field:
| Data type | Typical source of truth | Why |
|---|
| Contact info (name, email, phone) | CRM (Salesforce/HubSpot) | CRM is the canonical record |
| Activity data (emails, calls) | Engagement tool (Apollo/Salesloft/Mailshake) | Activity originates in the engagement tool |
| Deal/opportunity | CRM | Revenue data lives in CRM |
| Lead score | MAP or CRM | Scoring logic runs in MAP/CRM |
| Sequence status | Engagement tool | Sequence state managed by engagement tool |
Conflict resolution
- Last-write-wins: Simple but dangerous — later update overwrites earlier one
- Source-of-truth wins: Designated source always overwrites destination
- Field-level rules: Different rules per field (e.g., CRM wins for phone, engagement tool wins for email status)
- Manual review: Flag conflicts for human review (safest for critical fields)
Deduplication
- Match keys: Email address (primary), company domain + name (secondary)
- When to dedup: Before creating records, during sync, and periodically as maintenance
- Tools: Native CRM dedup (Salesforce Duplicate Rules, HubSpot dedup tool), or third-party (Dedupely, RingLead)
Error handling
- Retry logic: Implement exponential backoff for failed API calls (1s, 2s, 4s, 8s)
- Dead letter queue: Store failed events for manual review and replay
- Alerting: Slack/email notification when sync errors exceed threshold
- Monitoring: Track sync success rate, latency, and error types weekly
Gotchas
- Check native integrations first. Don't build a Zapier workflow for something the tools already handle natively. Native integrations are more reliable, handle edge cases better, and don't cost extra. Check Settings > Integrations in both tools before going custom.
- Respect API rate limits. Every tool has rate limits — Mailshake (100/min), Apollo (~200/min on Pro), Salesforce (varies), HubSpot (100/10s). High-volume syncs that ignore rate limits will get throttled or blocked. Always implement batching and backoff.
- Define source of truth before bidirectional sync. Bidirectional sync without clear field-level ownership creates data ping-pong (A updates B, B updates A, loop). For every field that syncs bidirectionally, document which tool wins on conflict.
Related skills
- — Qwilr-specific CRM integrations, API, and webhook events
- — Mailshake platform help including API and webhook details
- — Apollo platform help including CRM sync and API
- — Smartlead platform help including API and webhook details
- — Lemlist platform help including API and webhook details
- — Salesloft platform help including integrations
- — Groove.cm platform help including GrooveSell webhooks and Zapier integration
- — Yesware platform help (native Salesforce integration, no API)
- — Mixmax platform help including rules engine and integrations
- — Reply.io platform help including webhooks and integrations
- — Woodpecker platform help including API and webhook details
- — Email deliverability (relevant when integrating sending tools)
- — Not sure which skill to use? The router matches any sales objective to the right skill.
Examples
Example 1: Mailshake reply → Salesforce + Slack
User says: "When someone replies to my Mailshake campaign, I want to create a task in Salesforce and get a Slack notification."
Skill does:
- Checks if Mailshake-Salesforce native integration covers this (it does for activity sync)
- Recommends native for Salesforce + Zapier for Slack notification
- Provides Zapier workflow: Mailshake "Reply" trigger → Slack "Send Message" action
- Configures field mapping for the Salesforce activity
Result: Reply-to-task sync via native integration, Slack alert via Zapier
Example 2: Salesloft activity → HubSpot
User says: "I need to sync all Salesloft activity to HubSpot so our marketing team can see sales touchpoints."
Skill does:
- Checks native integration (Salesloft-HubSpot integration exists)
- Walks through native integration setup and field mapping
- Defines sync direction (Salesloft → HubSpot, one-way for activity)
- Addresses dedup and conflict resolution
Result: Native integration configured with clear sync direction and field mapping
Example 3: HubSpot MQL → Apollo sequence
User says: "When a lead hits MQL status in HubSpot, I want to auto-enroll them in an Apollo sequence."
Skill does:
- Designs trigger: HubSpot workflow on lifecycle stage = MQL
- Recommends Zapier (HubSpot trigger → Apollo "Add Contact to Sequence" action)
- Provides field mapping from HubSpot to Apollo contact fields
- Adds error handling (what if contact already exists in Apollo, what if sequence is full)
Result: MQL-triggered enrollment with field mapping and error handling
Troubleshooting
Sync creating duplicates
Symptom: Same contact appearing multiple times in destination tool
Cause: Missing dedup logic — sync creates new records instead of matching existing ones
Solution: Add matching/dedup step before create. Match on email address (primary key). Use CRM's native dedup rules. For Zapier, use "Find or Create" actions instead of "Create."
Events not firing
Symptom: Webhook or trigger not executing when expected
Cause: Webhook URL misconfigured, event type wrong, or tool's webhook delivery failing
Solution: Check webhook logs in the source tool. Test with a webhook debugging tool (webhook.site or RequestBin). Verify the event type matches exactly. Check if the webhook was disabled after errors.
Rate limit errors in high-volume sync
Symptom: 429 errors, sync falling behind, or events being dropped
Cause: Sending too many API requests too quickly
Solution: Implement batching (batch multiple records per request where API supports it). Add exponential backoff on 429 responses. Reduce sync frequency (every 5 min instead of real-time). Use bulk API endpoints where available.