We are currently saving the webhook events from Gravy in the jobs-gravy. Here's the form by which the event is sent and saved:
Here are the payloads from the Gravy webhook events: https://docs.gr4vy.com/guides/features/webhooks/payload
'{"type":"event","id":"36d2c101-4db5-4afd-ba4b-8fd9b60764ab","created_at":"2024-07-22T19:56:22.973896+00:00","target":{"type":"transaction","id":"b332ca0a-1dce-4ae6-b27b-04f70db8fae7"},"merchant_account_id":"default"}'We need to make another request to review the full transaction details and push to the relevant queues (like we do in the other jobs-{processor} queues), pending the time Gravy deploys the updates to their webhooks.