Pulsegate

Appearance

Sent to Make.com (Dashboard) ​

The dashboard includes a Sent to Make.com section so you can see which leads were sent to the Make.com webhook and inspect the exact payload for each send.

Access ​

  • Sidebar: Under Leads, Sent to Make.com (admin-only).
  • Route: /sent-to-make. Optional query: ?lead_id=123 to filter by lead.

Behaviour ​

  • When a payload is successfully sent to the Make.com webhook (from lead capture or testing leads), a copy is stored in the MakeWebhookSends table (migration 033). Each send includes a make_send_public_id (UUID) in the payload so Make.com can call back to link the execution.
  • The Sent to Make.com page lists these records with:
    • Quick range — Today, Yesterday, Past 7/14/30 days, All time, or Date range.
    • Search — By email, phone, or name (searches inside the stored payload JSON).
    • Pagination — Limit/offset with page size options.
  • Each row shows: Sent at, Name, Email, Phone, Project, Lead (link to lead detail), Execution (link to Make.com execution log when callback was used), and Payload (expand to view JSON, or copy to clipboard).
  • From lead detail, a View in Sent to Make.com button opens this page filtered by that lead (/sent-to-make?lead_id=…). From the table, the Lead column links back to the lead detail.
  • Make.com can call POST /lead.capture/make-callback (see Make callback API) with make_send_public_id (from the webhook payload) and make_execution_url (and optionally make_execution_id, make_execution_status). You can send any extra JSON in the same body; we store the full request body so the dashboard shows a View in Make.com link and the complete callback data (e.g. scenario name, duration, custom fields) in the payload panel under "Callback data from Make.com".

Data stored ​

  • MakeWebhookSends — One row per successful webhook send: Id, SentAt, LeadId (nullable), LeadSubmissionId (nullable), PayloadJson (full JSON sent to Make.com). From migration 037: PublicId, MakeExecutionUrl, MakeExecutionId, MakeExecutionStatus. From migration 038: MakeCallbackPayload (full JSON body from make-callback; any extra data from Make.com).
  • Logging is best-effort: if the table does not exist (migration not applied), the insert is skipped and no error is raised.

API ​

  • GET /analytics/leads/sent-to-make — Query params: period, date_from, date_to, q, lead_id, limit, offset. Admin only. Returns { sends, total }. When marketing role and PII masking is on, contact fields are masked.