Space Scoped Webhook Events
Events within the Space (when a user logs in or is updated, when a team is created or modified...etc) can be associated with a workflow by creating the workflow using the naming convention outlined below, and by configuring a webhook to call the configured workflow.
Action | Tree Source Group | Tree Name |
---|---|---|
Users Created | Users | Created |
Users Updated | Users | Updated |
Users Deleted | Users | Deleted |
Team Created | Teams | Created |
Team Updated | Teams | Updated |
Team Deleted | Teams | Deleted |
Datastore Form Created | Datastore Forms > [datastore-form-slug] | Created |
Datastore Form Updated | Datastore Forms > [datastore-form-slug] | Updated |
Datastore Submission Created | Datastore Submissions > [datastore-form-slug] | Created |
Datastore Submission Submitted | Datastore Submissions > [datastore-form-slug] | Submitted |
Form Created | [kapp-slug] > [form-slug] | Created |
Form Updated | [kapp-slug] > [form-slug] | Updated |
Submission Created | Submissions > [kapp-slug] > [form-slug] | Created |
Submission Submitted | Submissions > [kapp-slug] > [form-slug] | Submitted |
A few important things to note:
- Datastore Forms and Submissions have separate webhooks and tree groups from standard forms and submissions.
- Form actions and Submission actions are separate and have separate actions and tree paths. Form actions are when that actual form is created, updated, etc. Submission actions are when instances of that form/the form's data are created, submitted, etc.
Updated about 4 years ago