When an event is sent
Each event counts as one task in Zapier or Make.
Triggers
A notification fires on two families of triggers. Any selected trigger within a family is enough; when both families are selected, one of each must hold; a family left empty means “any”. New Hires and Job Postings notifications select CRM events only: their signal is on every event.
“Updated” means LoneScale sent a write to the record. A company found while the account update mapping is empty is associated but not written: its action is
unchanged and no event fires. Job Postings push accounts only: their events have no contact.
Delivery
POSTto the webhook URL,Content-Type: application/json, with the headers set on the webhook connection.- No answer (timeout, connection reset, DNS),
408,425,429and any5xxare retried: four attempts in all, 5 s, 30 s and 90 s apart. ARetry-Afterheader is honoured up to 2 minutes. Any other4xxis not retried. - An endpoint that stays down for three events in a row gets one attempt per event for the rest of the run.
- Every delivery is listed in Logs (Integrations, type
WEBHOOK) with the request, the answer and the number of attempts. A delivery that got no answer shows as an error with status599. - When the last delivery fails, the webhook shows Webhook error in Integrations → Webhook and on the notifications that use it, until a delivery or a test succeeds.
- Deduplicate on
event_id: a retry after a timeout or a CRM rate-limit retry can deliver the same event twice.
Repush
Pushing runs to the CRM again from the app (select them in the run history, then Push) evaluates the webhook notifications again for every contact or account it pushes, on what this push did:originisrepush, andevent_idends with#repush-<id>, one id per repush. Deduplicating onevent_idkeeps the repush events.- A record the repush finds again never fires
created:crm.contact.createdandcrm.account.createdonly fire when the repush creates a new record. - A push that fails sends
crm.sync.failed. - Contacts the CRM settings keep out of the push send nothing, and Slack notifications are not posted again.
origin to skip what your flow already did for the run, such as a round-robin assignment.
Resend notifications
Resend notifications in the run history (select runs, then Resend notifications) sends the webhook notifications of those runs again, without pushing anything to the CRM. Use it when your endpoint was down during the run, or to feed a flow you set up afterwards:- Each event is the run’s own: same
event_id, withoriginset toreplay. Deduplicating onevent_idskips what you already processed. - The events say what the run did: a contact the run created is still
created, andsync.synced_atis when the run pushed it. owner_idis the owner the run read. If the run read none (no webhook notification fired for that record), the replay reads it and keeps it for later replays.- Every webhook notification the workflow uses fires, with its triggers as they are now, including one added or edited after the run. A record the run did not notify can therefore get an event. Slack notifications are not posted again.
Payload
signal.type new_hire, no previous_contact and an empty input. A Job Postings event has no contact, previous_contact nor lead, the account’s fields in result and its job postings in jobs:
Fields
The
url of a record is a deep link to HubSpot or Salesforce, built from the ids above, so a flow can open or write back to the record immediately.
