sales-integration
Facilitates seamless integration of sales tools using webhooks and automation platforms like Zapier and Make for efficient CRM workflows.
Install this skill
or
0/100
Security score
The sales-integration skill was audited on Mar 28, 2026 and we found 24 security issues across 1 threat category. Review the findings below before installing.
Categories Tested
Security Issues
medium line 3
Webhook reference
SourceSKILL.md
| 1 | --- |
| 2 | name: sales-integration |
| 3 | description: "Connect sales tools with webhooks, Zapier/Make, native integrations, and custom API pipelines — CRM sync, event triggers, data mapping, and error handling. Use when connecting Mailshake/Apollo/Salesloft to CRM, setting up webhook pipelines, building Zapier/Make automations for sales workflows, syncing data between tools, or troubleshooting integration issues. Do NOT use for Qwilr-specific automations (use /sales-qwilr-automation), general CRM platform config (use /sales-apollo or /sales-salesloft), or marketing automation flows (use /email-sequence)." |
| 4 | argument-hint: "[describe source tool, destination tool, trigger event, and desired action]" |
| 5 | license: MIT |
medium line 132
Webhook reference
SourceSKILL.md
| 130 | **Implementation options**: |
| 131 | - Zapier: Trigger = Mailshake "Reply Received" → Actions = Salesforce "Create Task" + Slack "Send Message" |
| 132 | - Webhook: Mailshake push event (Reply) → your endpoint → Salesforce API + Slack API |
| 133 | - Native: Mailshake-Salesforce integration (auto-syncs replies as activities) |
| 134 |
medium line 153
Webhook reference
SourceSKILL.md
| 151 | **Implementation options**: |
| 152 | - **Zapier/Make (no-code)**: HubSpot "Lifecycle Stage Change" trigger → Apollo "Add Contact to Sequence" action. Easiest setup, handles auth automatically. |
| 153 | - **CRM webhook + custom API (low-code)**: HubSpot workflow triggers webhook → your endpoint calls Apollo `POST /contacts/add_to_emailer_campaign`. More control over field mapping, error handling, and conditional logic. |
| 154 | - **Native CRM workflow (if supported)**: Some CRM-to-engagement-tool integrations support enrollment triggers natively — check Settings > Integrations before building custom. |
| 155 |
medium line 180
Webhook reference
SourceSKILL.md
| 178 | - Handle duplicates (check if activity already exists before creating) |
| 179 | |
| 180 | ## Step 4 — Platform webhook reference |
| 181 | |
| 182 | ### Mailshake webhooks |
medium line 191
Webhook reference
SourceSKILL.md
| 189 | - **Setup**: Settings > Integrations > Webhooks |
| 190 | - **Events**: Contact created, contact updated, sequence enrollment, sequence completion, email bounced |
| 191 | - **Note**: Apollo's webhook support is more limited than Mailshake's. For complex automations, use the REST API with polling. |
| 192 | |
| 193 | ### Salesloft webhooks |
medium line 218
Webhook reference
SourceSKILL.md
| 216 | |
| 217 | ### Yesware integrations |
| 218 | - **No public API**: Yesware does not offer a public REST API. No webhook endpoints, no developer docs. |
| 219 | - **Integration methods**: Native connectors only — Salesforce (Enterprise plan), Gmail, Outlook, Zoom, LinkedIn, Clari, DocSend |
| 220 | - **Zapier**: Limited Zapier support — check Zapier for available triggers/actions (may be community-built, not official) |
medium line 226
Webhook reference
SourceSKILL.md
| 224 | ### Reply.io webhooks |
| 225 | - **Setup**: API endpoint `POST /webhooks` or via Settings > Integrations > Webhooks in dashboard |
| 226 | - **Events**: Contact replied, email sent, email opened, email clicked, email bounced, contact status changed, task created (specific event types available via `GET /webhook-events`) |
| 227 | - **Delivery management**: API endpoints for managing webhook delivery, retries, and failures |
| 228 | - **API versions**: V3 (beta) has full webhook management; V1/V2 have basic webhook support |
medium line 227
Webhook reference
SourceSKILL.md
| 225 | - **Setup**: API endpoint `POST /webhooks` or via Settings > Integrations > Webhooks in dashboard |
| 226 | - **Events**: Contact replied, email sent, email opened, email clicked, email bounced, contact status changed, task created (specific event types available via `GET /webhook-events`) |
| 227 | - **Delivery management**: API endpoints for managing webhook delivery, retries, and failures |
| 228 | - **API versions**: V3 (beta) has full webhook management; V1/V2 have basic webhook support |
| 229 | - **Full reference**: See `/sales-reply` → `references/reply-api-reference.md` |
medium line 228
Webhook reference
SourceSKILL.md
| 226 | - **Events**: Contact replied, email sent, email opened, email clicked, email bounced, contact status changed, task created (specific event types available via `GET /webhook-events`) |
| 227 | - **Delivery management**: API endpoints for managing webhook delivery, retries, and failures |
| 228 | - **API versions**: V3 (beta) has full webhook management; V1/V2 have basic webhook support |
| 229 | - **Full reference**: See `/sales-reply` → `references/reply-api-reference.md` |
| 230 |
medium line 233
Webhook reference
SourceSKILL.md
| 231 | ### Woodpecker webhooks |
| 232 | - **Setup**: API endpoint or via Settings > Integrations > Webhooks in dashboard |
| 233 | - **Events**: Prospect replied, email sent, email opened, email clicked, email bounced, prospect status changed, prospect interested (specific events via webhook management endpoints) |
| 234 | - **API access**: Requires API & integrations add-on (€20/mo) |
| 235 | - **Rate limits**: Same as main API — 1 concurrent request, queue of 6 |
medium line 241
Webhook reference
SourceSKILL.md
| 239 | - **Setup**: Dashboard at app.mixmax.com/dashboard/rules or API `POST /rules` with trigger and actions |
| 240 | - **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 |
| 241 | - **Action types**: Webhook call, Salesforce record update, sequence enrollment, task creation, Slack notification |
| 242 | - **Advanced rules**: Growth+CRM plan — trigger on Salesforce objects, use complex logic (AND/OR conditions) |
| 243 | - **API**: `GET/POST /rules`, `PATCH/DELETE /rules/:id`, `POST/GET /rules/:id/actions` |
medium line 244
Webhook reference
SourceSKILL.md
| 242 | - **Advanced rules**: Growth+CRM plan — trigger on Salesforce objects, use complex logic (AND/OR conditions) |
| 243 | - **API**: `GET/POST /rules`, `PATCH/DELETE /rules/:id`, `POST/GET /rules/:id/actions` |
| 244 | - **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. |
| 245 | |
| 246 | ### Tomba webhooks |
medium line 248
Webhook reference
SourceSKILL.md
| 246 | ### Tomba webhooks |
| 247 | - **Setup**: Pass `webhook_url` parameter on supported API endpoints (domain search, email finder, enrichment, LinkedIn finder, author finder, bulk operations) |
| 248 | - **Events**: Async result delivery — when a lookup or bulk job completes, Tomba POSTs results to your webhook URL |
| 249 | - **Plan requirement**: Webhooks require Pro plan or above |
| 250 | - **Note**: Tomba's webhook model is callback-based (per-request), not event-subscription-based. You provide a URL on each API call rather than registering a persistent webhook endpoint. |
medium line 250
Webhook reference
SourceSKILL.md
| 248 | - **Events**: Async result delivery — when a lookup or bulk job completes, Tomba POSTs results to your webhook URL |
| 249 | - **Plan requirement**: Webhooks require Pro plan or above |
| 250 | - **Note**: Tomba's webhook model is callback-based (per-request), not event-subscription-based. You provide a URL on each API call rather than registering a persistent webhook endpoint. |
| 251 | |
| 252 | ### Seismic webhooks |
medium line 258
Webhook reference
SourceSKILL.md
| 256 | |
| 257 | ### Qwilr webhooks |
| 258 | - **Full reference**: See `/sales-qwilr-automation` for Qwilr-specific webhook events and CRM integrations |
| 259 | |
| 260 | ## Step 5 — Data sync best practices |
medium line 298
Webhook reference
SourceSKILL.md
| 296 | ## Related skills |
| 297 | |
| 298 | - `/sales-qwilr-automation` — Qwilr-specific CRM integrations, API, and webhook events |
| 299 | - `/sales-mailshake` — Mailshake platform help including API and webhook details |
| 300 | - `/sales-apollo` — Apollo platform help including CRM sync and API |
medium line 299
Webhook reference
SourceSKILL.md
| 297 | |
| 298 | - `/sales-qwilr-automation` — Qwilr-specific CRM integrations, API, and webhook events |
| 299 | - `/sales-mailshake` — Mailshake platform help including API and webhook details |
| 300 | - `/sales-apollo` — Apollo platform help including CRM sync and API |
| 301 | - `/sales-smartlead` — Smartlead platform help including API and webhook details |
medium line 301
Webhook reference
SourceSKILL.md
| 299 | - `/sales-mailshake` — Mailshake platform help including API and webhook details |
| 300 | - `/sales-apollo` — Apollo platform help including CRM sync and API |
| 301 | - `/sales-smartlead` — Smartlead platform help including API and webhook details |
| 302 | - `/sales-lemlist` — Lemlist platform help including API and webhook details |
| 303 | - `/sales-salesloft` — Salesloft platform help including integrations |
medium line 302
Webhook reference
SourceSKILL.md
| 300 | - `/sales-apollo` — Apollo platform help including CRM sync and API |
| 301 | - `/sales-smartlead` — Smartlead platform help including API and webhook details |
| 302 | - `/sales-lemlist` — Lemlist platform help including API and webhook details |
| 303 | - `/sales-salesloft` — Salesloft platform help including integrations |
| 304 | - `/sales-groove` — Groove.cm platform help including GrooveSell webhooks and Zapier integration |
medium line 308
Webhook reference
SourceSKILL.md
| 306 | - `/sales-mixmax` — Mixmax platform help including rules engine and integrations |
| 307 | - `/sales-reply` — Reply.io platform help including webhooks and integrations |
| 308 | - `/sales-woodpecker` — Woodpecker platform help including API and webhook details |
| 309 | - `/sales-deliverability` — Email deliverability (relevant when integrating sending tools) |
| 310 | - `/sales-seismic` — Seismic platform help including integrations, LiveSend, and Digital Sales Rooms |
medium line 311
Webhook reference
SourceSKILL.md
| 309 | - `/sales-deliverability` — Email deliverability (relevant when integrating sending tools) |
| 310 | - `/sales-seismic` — Seismic platform help including integrations, LiveSend, and Digital Sales Rooms |
| 311 | - `/sales-tomba` — Tomba platform help including API, webhook callbacks, and CRM integrations |
| 312 | - `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. |
| 313 |
medium line 351
Webhook reference
SourceSKILL.md
| 349 | |
| 350 | ### Events not firing |
| 351 | **Symptom**: Webhook or trigger not executing when expected |
| 352 | **Cause**: Webhook URL misconfigured, event type wrong, or tool's webhook delivery failing |
| 353 | **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. |
medium line 352
Webhook reference
SourceSKILL.md
| 350 | ### Events not firing |
| 351 | **Symptom**: Webhook or trigger not executing when expected |
| 352 | **Cause**: Webhook URL misconfigured, event type wrong, or tool's webhook delivery failing |
| 353 | **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. |
| 354 |
medium line 353
Webhook reference
SourceSKILL.md
| 351 | **Symptom**: Webhook or trigger not executing when expected |
| 352 | **Cause**: Webhook URL misconfigured, event type wrong, or tool's webhook delivery failing |
| 353 | **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. |
| 354 | |
| 355 | ### Rate limit errors in high-volume sync |
Scanned on Mar 28, 2026
View Security DashboardRate this skill
Categorysales
UpdatedApril 4, 2026
openclawapisdrsales-operationsbusiness-developmentcustomer-success-manageraccount-executivezapiermakesalesforcehubspotmailchimppipedriveslacksales
sales-skills/sales