Once you have created a webhook from Tomorro, you will be able to test it, and verify that it works correctly.
⚡️ Test the Webhook
In order to receive a payload with the data you are interested in, you must :
create a mock project on Tomorro (which you can delete later)
you can then send it for signature and define yourself as a signatory for both parties so that the data related to the signature of a project is also retrieved
finally, for data related to reminders, you can, when you create the project, add a fixed date for the reminder and link it to the end or renewal date for example
✅ Success of the webhook
In case the webhook was successful, then you will receive a different payload for each event. You will get the name of the contract, the name of the co-contractor, the name of the template used, but also other more specific information depending on the type of event triggered such as the name of the deadline callback.
Nom de l'événement | Description de l'événement |
contractCreated | Un nouveau contrat a été créé |
contractSigned | Un nouveau contrat a été signé |
👨👨👧 Access Rights
The webhook will be triggered according to the access rights of the person who set it up. This means, that an event will be triggered only when a project is created and signed and the person who owns the webhook has access to it.
We therefore recommend that you ask an ADMIN to set up the webhooks if your goal is to be alerted as soon as a project is created, regardless of the model used, the creator or the access rights on this contract.
🔂 Retry policy
If the webhook responds with an other code than a 2xx or if the webhook take too much time (the timeout is set to 3s for the moment but the value may change), we consider the try as failed.
In this case, if the number of tries for this WebhookEvent is less than the max allowed (currently MAX_RETRIES = 3 ), we publish a new event in the queue with a delay of 5min (same here, value may change).
Otherwise, we don’t retry and disable the webhook.