The parts
The life of an event
1
Receive
A push source gets an HTTP request. A mail or polled source finds new data. hooksnode checks the signature (if set), the rate limit and your credits.
2
Save
hooksnode writes the event to the database before it queues anything. If the server stops after the write, a job finds the event and queues it again.
3
Fan out
hooksnode makes one delivery for each active destination that takes events from this source. Each delivery has its own queue, so a slow destination does not stop the others.
4
Prepare
For each delivery, hooksnode applies the destination’s transform, then its filter, then its extra headers. Then it adds the signature.
5
Deliver
hooksnode sends the request. A
2xx response is a success. Any other result is a failed attempt. hooksnode tries again with backoff, up to 25 attempts.Event statuses
Delivery statuses
A filtered delivery shows as
delivered with status code 0 and the response {"filtered":true}.