Webhooks and background jobs
Caraer apps can react to record events and date-due events, receive inbound requests, run scheduled functions, and queue background work. These capabilities connect activity in Caraer with processing in your product.
Why integrate
Section titled “Why integrate”Your service can respond when relevant business data changes. Longer tasks can run separately from the user’s request, while installation settings and permissions keep processing tied to the correct company.
What you could build
Section titled “What you could build”When a record becomes ready for processing, a webhook could start document generation in your service. Your service could return a callback to a declared inbound route, and a background job could write the result to the original record.
Start integrating
Section titled “Start integrating”Read App jobs and webhooks for event payloads, schedules, inbound authentication, and recovery. Use serverless functions for the runtime contract and app settings for configurable object selections.
Handlers should tolerate retries and repeated notifications. Choose the payload format and fields your task needs, and return quickly when work should be queued. A stopped subscription requires explicit recovery under the documented failure policy; testing or redeploying configuration does not reactivate it or replay old events.