Create the Make scenario

  • Create a new Make scenario.
  • Add a Custom webhook instant trigger.
  • Copy the generated webhook URL.
  • Run the scenario once so Make waits for sample data.
  • Create an InstaChime CRM webhook destination that points to the Make URL.

Map fields

  • `lead.id` -> unique lead identifier.
  • `lead.customer_name` -> contact name.
  • `lead.email` -> email address.
  • `lead.phone` -> phone number.
  • `lead.source_platform` -> source platform or channel.
  • `lead.campaign` -> campaign, form, or offer context.
  • `lead.lead_score`, `lead.sentiment`, `lead.company_domain` -> optional routing and reporting fields.

Sample payload

{
  "event": "lead.created",
  "lead": {
    "id": "lead_uuid",
    "customer_name": "Jamie Lee",
    "email": "jamie@example.com",
    "phone": "+15555550123",
    "source_platform": "google_ads",
    "campaign": "Emergency demo campaign",
    "message": "Need pricing today",
    "lead_score": 82,
    "sentiment": "urgent",
    "company_domain": "example.com"
  }
}

Build common routes

  • Route urgent leads to Slack/Teams and a CRM.
  • Append every lead to Google Sheets or Excel Online.
  • Create or update contacts in HubSpot, Salesforce, Pipedrive, HighLevel, or Zoho.
  • Filter by source platform, lead score, campaign, or territory before sending to each module.

Verify

  • Send an InstaChime sample delivery while the scenario is listening.
  • Confirm Make detects the payload structure.
  • Run the scenario and confirm every target module succeeds.
  • Confirm the Make run ID or final app record ID is visible in the destination response.
  • Share the scenario link only after removing private credentials from shareable instructions.

Exact Make setup

  • Open Make and create a new scenario.
  • Add Webhooks as the first module.
  • Choose Custom webhook.
  • Create a new webhook and give it a clear name such as `InstaChime lead.created`.
  • Copy the generated webhook URL.
  • Click Run once so Make starts listening.
  • Open InstaChime `/integrations`.
  • Create a CRM webhook destination using the Make URL.
  • Send a sample delivery from InstaChime.
  • Confirm Make detects the payload and shows the `lead` bundle.
  • Add the next module for Google Sheets, Excel, HubSpot, Salesforce, Pipedrive, HighLevel, Zoho, Slack, Teams, or another target.
  • Map the lead fields and run the scenario once end to end.
  • Enable the scenario schedule.

Make routing and filters

  • Add a Router after the webhook if multiple destinations need different rules.
  • Add filters by source platform, campaign, lead score, sentiment, territory, or service request.
  • Send urgent leads to chat and CRM immediately.
  • Send every lead to a spreadsheet or audit table if that is part of your reporting process.
  • Use error handlers or a datastore if a downstream module needs retry control beyond Make defaults.

Make response and verification

  • Use the default webhook response unless your receiver path requires a specific response.
  • Capture the Make run ID or destination record ID in logs where possible.
  • Confirm InstaChime delivery history shows HTTP 200 from Make.
  • Confirm each downstream Make module has a successful operation in the scenario history.
  • If you share a scenario, remove private URLs, tokens, and account-specific IDs from notes before sharing.

Make troubleshooting

  • If Make does not detect the payload, click Run once before sending the sample from InstaChime.
  • If fields appear as empty, inspect the captured webhook bundle and remap from the `lead` object.
  • If a module fails after the webhook, open the failed scenario run and inspect that module response.
  • If Make returns non-2xx to InstaChime, check scenario status and webhook availability.
  • If a shared scenario breaks, recreate the webhook URL under the account that will own the live scenario.

Official references

These vendor-owned pages explain the controls and requirements referenced in this guide.

  • Make webhooksOfficial documentation used to verify this setup path and its current vendor requirements.
  • Make hooks APIOfficial documentation used to verify this setup path and its current vendor requirements.
  • Make scenario sharingOfficial documentation used to verify this setup path and its current vendor requirements.
  • Make Webhooks app helpOfficial documentation used to verify this setup path and its current vendor requirements.