Skip to content
Download PDF guide

Event types ​

Every significant action in your organization emits one of 43 event types. These events drive both workflows (automations inside the platform) and webhooks (deliveries to your own systems), so the same catalog applies to both.

Assignments ​

EventFires whenTypical automation use
assignment.createdA new assignment is created.Notify the team that new work is available.
assignment.updatedAssignment details (name, reference, fields) change.Sync changes to your claim system.
assignment.status_changedAn assignment moves to a new status.Email the claims inbox on every status move.
assignment.archivedAn assignment is archived.Close out the record in external systems.

Users ​

EventFires whenTypical automation use
user.createdA user is added to the org.Send a welcome message or provision accounts elsewhere.
user.updatedA user's name or role changes.Keep an HR directory in sync.
user.deactivatedA user is deactivated.Revoke access in connected systems.
user.deletedA user is deleted.Final cleanup in connected systems.

Invitations ​

EventFires whenTypical automation use
invitation.sentAn assignment-level invitation is sent.Log outreach to contractors.
invitation.acceptedAn invitee accepts access.Notify the assignment owner the person they shared it with is in.
invitation.revokedAn invitation or grant is revoked.Confirm access removal for compliance records.

Access ​

EventFires whenTypical automation use
access.grantedA person is granted access to an assignment.Audit trail forwarding to a security system.
access.revokedAccess is removed.Confirm offboarding of a contractor.

Locations (rooms) ​

EventFires whenTypical automation use
location.createdA room is added to an assignment.Track scope growth on a loss.
location.updatedA room's name, order, assignee, or notes change.Keep external room lists current.
location.deletedA room is soft-deleted.Flag scope changes for review.
location.claimedA field user claims a room to work it.See rooms being picked up in real time.
location.unclaimedA claimed room is released.Spot rooms going back to the pool.
location.completedA room is marked complete.Track per-room progress toward assignment completion.

Groups ​

EventFires whenTypical automation use
group.createdA media group is created.Mirror organizational structure externally.
group.updatedA group changes. When a group is switched between items and scoping, data.fields is ["intent"] and data.intent is the new value.Keep external groupings in sync.
group.deletedA group is removed.Clean up mirrored structures.

People ​

EventFires whenTypical automation use
person.createdA person record is added.Populate a contacts database.
person.updatedA person record changes.Keep contact details in sync.

Media ​

EventFires whenTypical automation use
media.capturedA photo, video, or audio clip is captured on a device.Real-time capture notifications.
media.uploadedOne file of a media item (the full size original, the preview copy, or the thumbnail) finishes uploading. Fires once per file.Backups of individual files.
media.syncedA photo or video has fully synced: both the original and the preview copy are safely stored. Fires exactly once per item.Send new media to ContentsVision, or any outside processing.
media.upload_failedAn upload fails.Alert team admins to connectivity problems.
media.updatedA media item changed. From the console: a note is added or edited (console tag changes fire tag.applied / tag.removed instead). From the field app: the photo is moved to another room or group, its tags or note change, or it is marked or unmarked as a scoping shot (intent) or its item marks change (marks). Also fires when a new original file replaces an already synced one, and once for each photo in a group that is switched between items and scoping (data.via is group). data.fields lists what changed.Keep an outside copy of the media in step.
media.deletedA media item is deleted, from the console or the field app.Record deletions for compliance, or remove the item downstream.

Every media event carries the assignment, room, and group the item belongs to (data.assignmentId, data.locationId, data.groupId) and its type (data.type: photo, video, or audio), so a workflow always knows which job the media is part of.

Submissions ​

EventFires whenTypical automation use
submission.createdA locked hand-off is submitted from the field.SMS the team's admins that work has landed.

Tags ​

Applying a tag fires the event on the thing that was tagged, with data.tags listing the exact tag names that changed and data.assignmentId carrying the job, so a workflow can trigger on one tag in particular. See Tags in workflows.

EventFires whenTypical automation use
tag.appliedA tag is put on an assignment, room, or media item.Escalate the moment somebody marks a job urgent.
tag.removedA tag is taken off one.Clear a downstream flag when review finishes.
tag.createdA new tag is defined for the organization.Mirror the vocabulary into another system.
tag.updatedA tag is renamed or recoloured.Keep an external mapping in step with a rename.
tag.deletedA tag is deleted from the organization.Warn when a tag an integration depends on disappears.

Workflow-applied tags do not retrigger workflows

A tag applied by a workflow is recorded as a system action, and system actions never start another workflow. A flow that tags on tag.applied cannot spin.

Profiles ​

EventFires whenTypical automation use
profile.createdA new capture profile draft is created.Track profile authoring activity.
profile.publishedA profile is published and becomes usable.Notify admins a new form is live.
profile.archivedA profile is retired.Stop using the profile in external intake tools.

Webhooks and integrations ​

EventFires whenTypical automation use
webhook.endpoint.createdA webhook endpoint is added.Security monitoring of integration changes.
webhook.delivery.failedA webhook delivery fails.Page the integrations owner when deliveries break.
integration.token.createdAn integration token is issued.Log credential issuance for audit.
integration.token.revokedAn integration token is revoked.Confirm credential retirement.

Same events, two consumers

Everything in this catalog can trigger a workflow in the console and can be delivered to a webhook endpoint. Use workflows for messages and status changes; use webhooks when your own systems need the raw event.