OyeChats
FeaturesSolutionsIntegrationsPricingDocsBlogContact us

Connecting a CRM

There is no per-CRM connector. There is one webhook and an automation platform, which reaches every CRM including yours.

How it works

OyeChats sends signed webhooks. Zapier, Make, n8n and every other automation platform can catch a webhook and write to a CRM. That composition covers HubSpot, Salesforce, Pipedrive, Zoho and anything else with an automation connector, and your own backend, if you would rather skip the middle layer.

Set expectations honestly. There are no native, one-click CRM connectors today. The dashboard ships setup guides for the Zapier and Make routes; anything described as a "HubSpot integration" is that pattern.

HubSpot via Zapier

  1. Create a Zap

    Trigger: Webhooks by Zapier → Catch Hook.

  2. Copy the Zapier webhook URL

    Zapier shows it once the trigger is created.

  3. Register it in OyeChats

    Workspace → Integrations → Webhook endpoints. Subscribe it to tier_transition, and to lead_captured if you want every contact rather than only qualified ones.

  4. Add the action

    HubSpot → Create or update contact.

  5. Map the fields

    Email from data.contact.email on lead_captured; tier and score from data.new_tier and data.score on tier_transition.

  6. Send a test and turn it on

    Use the Test button in OyeChats and confirm the record lands.

Salesforce via Make

  1. Create a scenario

    Trigger: Webhooks → Custom webhook.

  2. Copy the Make webhook URL

    And register it in OyeChats against your chosen events.

  3. Add the Salesforce module

    Create a record → Lead.

  4. Map the payload

    Email, name, company from the payload, plus score and tier into custom fields.

Patterns that work well

Only route qualified leads
Subscribe to tier_transition and filter on new_tier == "sql" in your automation. Your sales team gets the leads worth calling and nothing else.
Two events, one record
lead_captured creates or updates the contact; tier_transition enriches it with the score. Key both on session_id.
Backfill the rest with the API
When you need the transcript or the dimension breakdown, call GET /leads/{session_id} from your automation using the session_id in the payload.
Alert instead of writing
The same webhook can post to Slack or Teams. The fastest useful integration for a small team is often a channel message, not a CRM record.

Something here wrong or missing? Tell us and name this page. We will fix it.