Skip to content

23 October 2026: Richer relation webhooks, file visibility on record writes, and webhook recovery

Section titled “Identify changed links in MINIMAL relation webhooks”

Available in production, MINIMAL relation webhooks now include event.type, event.relationName, and UUID/object-name identities in event.fromRecord and event.toRecord. Receivers can identify created, updated, and deleted links while preserving their original direction. Endpoint properties, user data, and context remain excluded.

No action is required. To use the new fields, see the payload example.

File visibility is applied before record writes return success

Section titled “File visibility is applied before record writes return success”

Available in production, record creates and updates now apply configured visibility to adopted company files before returning success, including when lifecycle events are disabled. Attachment linking remains asynchronous.

If storage cannot apply visibility, the request returns HTTP 500 even though the record and committed files remain saved. Read the record before retrying. See record file visibility.

The deployed app and published CLI 0.1.12 now support recovery of automatically deactivated company webhooks. The app’s Webhooks list and editor show an Automatically deactivated warning with the HTTP status and time. CLI commands caraer webhooks list and caraer webhooks show expose runtime status for the selected company.

After repairing the destination, use Reactivate in the app or run caraer webhooks reactivate <webhook-uuid> --app <app-uuid> with webhook edit permissions. CLI recovery requires version 0.1.12. Reactivation resumes future deliveries and resets the failure counter; old queued events are not replayed, so verify delivery with a new event. Failed app reactivation leaves the warning visible; ordinary tests and edits remain available.

See the CLI workflow and app recovery guide.

See the urgent announcement already published this week.