Send CRM deals and calls by webhook

Your Webhook URL

Every tool posts to your webhook source’s URL with the tool’s name added at the end:

POST https://api.srctk.com/api/webhooks/incoming/<your webhook key>/<tool>

• Keep the URL private: anyone who has it can send conversions to your site. If it is shared by mistake, rotate the source in SourceTrack to get a new one.
• Leave request signing off for this source. These tools do not add SourceTrack’s signature header, so a signed source refuses their deliveries.

Not Supported

• HubSpot Webhooks API (a HubSpot app’s subscriptions): it sends a list of events without the deal amount or the contact’s email, and SourceTrack refuses it. Use the HubSpot workflow below.
• Salesforce Outbound Messages: they are XML, and SourceTrack reads JSON only, so they are refused. Use the Salesforce Flow below.

HubSpot: Send a Webhook from a Deal Workflow

1. In HubSpot, go to Automation → Workflows and open a deal-based workflow that starts when a deal reaches your won stage.
2. Click + to add an action, and under Data ops choose Send a webhook.
3. Set the method to POST and the webhook URL to your URL ending in /hubspot.
4. Choose Customize request body and add each key below. For a property, type the key and select the HubSpot property. For a static value, type the key and the value.

A custom pipeline’s won stage reaches SourceTrack as a stage number, not as “closed won”. The static conversion_type is what marks the deal as won, so keep it in the won-stage workflow only. HubSpot offers the Send a webhook action on Data Hub Professional or Enterprise.

GoHighLevel: Use the Workflow Webhook Action

1. In GoHighLevel, go to Automation and open a workflow whose trigger is about an opportunity, for example a status or stage change.
2. Click + and add the Webhook action. POST is the default method.
3. Paste your URL ending in /ghl. No custom body is needed.

The action already sends the contact’s email and gclid and the opportunity’s id, status, lead_value and stage name (GoHighLevel spells that key pipleline_stage). A won opportunity is recorded as closed won with its lead value, and an open one by its stage name.

NoteGoHighLevel sends no currency. To send one, add a Custom Data item with the key currency and your currency code as the value. GoHighLevel does not say where Custom Data appears in the body, so check it under Recent payloads on your webhook source.

Salesforce: Send JSON from a Flow

1. In Salesforce Setup, create an External Credential and a Named Credential whose URL is https://api.srctk.com.
2. In Flow Builder, in a flow that runs when an opportunity is won, add an Action and choose Create HTTP Callout.
3. Pick that Named Credential, choose POST, and set the URL path to /api/webhooks/incoming/<your webhook key>/salesforce.
4. When Salesforce asks for a sample request, paste the JSON below.
5. Set each field from the opportunity: Id, StageName, IsWon, Amount, CurrencyIsoCode (only in orgs with more than one currency) and Email from the opportunity’s contact. Leave out st_aid and gclid if you do not store them.

{
  "Id": "0065e000002ABCXYZ",
  "StageName": "Closed Won",
  "IsWon": true,
  "Amount": 48000,
  "CurrencyIsoCode": "EUR",
  "Email": "buyer@example.com",
  "st_aid": "",
  "gclid": ""
}

IsWon set to true marks the deal as won, whatever your won stage is called.

CallRail and CallTrackingMetrics: Post-Call Webhooks

Only an answered inbound call of at least 60 seconds becomes a conversion, recorded as a phone call. Other calls are acknowledged and not recorded.

What Is Checked and What Is Not

• Checked against each tool’s documentation (30 October 2026): the field names in these templates, HubSpot’s Send a webhook steps, GoHighLevel’s Webhook action fields, the Salesforce Opportunity field names, and CallRail’s and CallTrackingMetrics’ webhook settings.
• Not yet checked against a captured delivery: the exact body each tool sends, including how it formats amounts, where GoHighLevel puts Custom Data, and where CallTrackingMetrics puts click IDs other than gclid.

Common Problems

• The tool shows a 401 error: the key in the URL is wrong, or the source was rotated or deleted. Copy the URL again.
• The tool shows a 422 error: SourceTrack could not read the body. Check that the tool sends JSON, and that you used the workflow or Flow above, not HubSpot’s Webhooks API or a Salesforce Outbound Message.
• Deals arrive without an amount: check the amount key in your template. A deal with no amount is recorded without a value rather than as zero.
• Deals have no source: the deal carried no visitor ID, click ID or email that SourceTrack could match.