Workflow Events

Workflow events are the provider or system signals that can start a Dawn workflow. This page lists the event IDs Dawn understands and the source kinds each event can be saved against.

Event Descriptor Fields

Dawn exposes workflow event support through GET /api/v1/workspaces/{workspaceId}/workflow-event-support. Use that live endpoint when building workflows programmatically.

Field	Meaning
`providerId`	Provider that owns the event, such as `github`, `azure_devops`, or `dawn`.
`eventType`	Dawn event ID used in workflow trigger requests.
`nativeEventId`	Provider webhook or system event name that Dawn normalizes.
`displayName`	Human-readable event name.
`description`	Human-readable explanation.
`category`	Group used by the UI.
`subjectKind`	Normalized subject kind that the workflow run receives.
`requiredSourceKinds`	Compatible source kinds. The selected source must match one of these kinds.
`supportsAutomaticWebhookRegistration`	Whether Dawn can register provider hooks automatically for this event.
`manualSetupNotes`	Setup guidance when the provider requires manual webhook configuration.

requiredSourceKinds is a compatibility set, not a list of sources that must all be selected. Pick one compatible source. For Azure DevOps, Dawn also treats project-scoped source kinds as compatible with events that include azure_devops.project.

System Events

Event type	Native event	Subject	Source kinds
`dawn.schedule.elapsed`	`dawn.schedule.elapsed`	`schedule`	None
`dawn.workspace_member.joined`	`dawn.workspace_member.joined`	`workspace_member`	None

GitHub Events

Automatic webhook registration is supported for GitHub events.

Event type	Native event	Subject	Source kinds
`github.pull_request.created`	`pull_request.opened`	`pull_request`	`github.repo`, `github.pull_request`
`github.pull_request.updated`	`pull_request.synchronize`	`pull_request`	`github.repo`, `github.pull_request`
`github.pull_request.commented`	`issue_comment.created`	`pull_request`	`github.repo`, `github.pull_request`
`github.pull_request.review_thread.updated`	`pull_request_review_thread.resolved`	`pull_request`	`github.repo`, `github.pull_request`
`github.issue.created`	`issues.opened`	`issue`	`github.repo`, `github.issue`
`github.issue.updated`	`issues.edited`	`issue`	`github.repo`, `github.issue`
`github.issue.commented`	`issue_comment.created`	`issue`	`github.repo`, `github.issue`
`github.actions.workflow_run.requested`	`workflow_run.requested`	`workflow_run`	`github.repo`, `github.pull_request`
`github.actions.workflow_run.in_progress`	`workflow_run.in_progress`	`workflow_run`	`github.repo`, `github.pull_request`
`github.actions.workflow_run.completed`	`workflow_run.completed`	`workflow_run`	`github.repo`, `github.pull_request`
`github.actions.workflow_job.queued`	`workflow_job.queued`	`workflow_job`	`github.repo`, `github.pull_request`
`github.actions.workflow_job.waiting`	`workflow_job.waiting`	`workflow_job`	`github.repo`, `github.pull_request`
`github.actions.workflow_job.in_progress`	`workflow_job.in_progress`	`workflow_job`	`github.repo`, `github.pull_request`
`github.actions.workflow_job.completed`	`workflow_job.completed`	`workflow_job`	`github.repo`, `github.pull_request`

Azure DevOps Events

Automatic webhook registration is supported for Azure DevOps Service Hooks.

Event type	Native event	Subject	Source kinds
`azure_devops.pull_request.created`	`git.pullrequest.created`	`pull_request`	`azure_devops.project`, `azure_devops.repo`, `azure_devops.pull_request`
`azure_devops.pull_request.updated`	`git.pullrequest.updated`	`pull_request`	`azure_devops.project`, `azure_devops.repo`, `azure_devops.pull_request`
`azure_devops.pull_request.commented`	`ms.vss-code.git-pullrequest-comment-event`	`pull_request`	`azure_devops.project`, `azure_devops.repo`, `azure_devops.pull_request`
`azure_devops.work_item.created`	`workitem.created`	`work_item`	`azure_devops.project`, `azure_devops.work_item`
`azure_devops.work_item.updated`	`workitem.updated`	`work_item`	`azure_devops.project`, `azure_devops.work_item`
`azure_devops.work_item.commented`	`workitem.commented`	`work_item`	`azure_devops.project`, `azure_devops.work_item`
`azure_devops.build.completed`	`build.complete`	`build`	`azure_devops.project`, `azure_devops.build`
`azure_devops.pipeline.run_state_changed`	`ms.vss-pipelines.run-state-changed-event`	`pipeline_run`	`azure_devops.project`, `azure_devops.pipeline`
`azure_devops.pipeline.job_state_changed`	`ms.vss-pipelines.job-state-changed-event`	`pipeline_job`	`azure_devops.project`, `azure_devops.pipeline`

Bitbucket Events

Bitbucket webhook setup is manual. Use the generated Dawn webhook URL and setup secret.

Event type	Native event	Subject	Source kinds
`bitbucket.pull_request.created`	`pullrequest:created`	`pull_request`	`bitbucket.repo`, `bitbucket.pull_request`
`bitbucket.pull_request.updated`	`pullrequest:updated`	`pull_request`	`bitbucket.repo`, `bitbucket.pull_request`
`bitbucket.pull_request.commented`	`pullrequest:comment_created`	`pull_request`	`bitbucket.repo`, `bitbucket.pull_request`
`bitbucket.pull_request.approved`	`pullrequest:approved`	`pull_request`	`bitbucket.repo`, `bitbucket.pull_request`
`bitbucket.pull_request.merged`	`pullrequest:fulfilled`	`pull_request`	`bitbucket.repo`, `bitbucket.pull_request`
`bitbucket.pull_request.declined`	`pullrequest:rejected`	`pull_request`	`bitbucket.repo`, `bitbucket.pull_request`
`bitbucket.issue.created`	`issue:created`	`issue`	`bitbucket.repo`, `bitbucket.issue`
`bitbucket.issue.updated`	`issue:updated`	`issue`	`bitbucket.repo`, `bitbucket.issue`
`bitbucket.issue.commented`	`issue:comment_created`	`issue`	`bitbucket.repo`, `bitbucket.issue`
`bitbucket.repo.push`	`repo:push`	`push`	`bitbucket.repo`
`bitbucket.build_status.updated`	`repo:commit_status_updated`	`build_status`	`bitbucket.repo`, `bitbucket.pull_request`

GitLab Events

GitLab webhook setup is manual. Use the generated Dawn webhook URL and setup secret.

Event type	Native event	Subject	Source kinds
`gitlab.merge_request.created`	`Merge Request Hook.open`	`merge_request`	`gitlab.repo`, `gitlab.merge_request`
`gitlab.merge_request.updated`	`Merge Request Hook.update`	`merge_request`	`gitlab.repo`, `gitlab.merge_request`
`gitlab.merge_request.commented`	`Note Hook.MergeRequest`	`merge_request`	`gitlab.repo`, `gitlab.merge_request`
`gitlab.issue.created`	`Issue Hook.open`	`issue`	`gitlab.repo`, `gitlab.issue`
`gitlab.issue.updated`	`Issue Hook.update`	`issue`	`gitlab.repo`, `gitlab.issue`
`gitlab.issue.commented`	`Note Hook.Issue`	`issue`	`gitlab.repo`, `gitlab.issue`
`gitlab.pipeline.status_changed`	`Pipeline Hook`	`pipeline`	`gitlab.repo`, `gitlab.merge_request`
`gitlab.job.status_changed`	`Job Hook`	`job`	`gitlab.repo`, `gitlab.merge_request`

Jira Events

Jira webhook setup is manual.

Event type	Native event	Subject	Source kinds
`jira.issue.created`	`jira:issue_created`	`issue`	`jira.issue`
`jira.issue.updated`	`jira:issue_updated`	`issue`	`jira.issue`
`jira.issue.deleted`	`jira:issue_deleted`	`issue`	`jira.issue`
`jira.issue.commented`	`comment_created`	`issue_comment`	`jira.issue`
`jira.issue.comment_updated`	`comment_updated`	`issue_comment`	`jira.issue`
`jira.issue.comment_deleted`	`comment_deleted`	`issue_comment`	`jira.issue`

Linear Events

Linear webhook setup is manual.

Event type	Native event	Subject	Source kinds
`linear.issue.created`	`Issue.create`	`issue`	`linear.issue`
`linear.issue.updated`	`Issue.update`	`issue`	`linear.issue`
`linear.issue.removed`	`Issue.remove`	`issue`	`linear.issue`
`linear.comment.created`	`Comment.create`	`comment`	`linear.issue`
`linear.comment.updated`	`Comment.update`	`comment`	`linear.issue`

Trello Events

Trello webhook setup is manual.

Event type	Native event	Subject	Source kinds
`trello.card.created`	`createCard`	`card`	`trello.card`
`trello.card.updated`	`updateCard`	`card`	`trello.card`
`trello.card.moved`	`updateCard.list`	`card`	`trello.card`
`trello.card.commented`	`commentCard`	`card`	`trello.card`
`trello.card.due`	`updateCard.due`	`card`	`trello.card`
`trello.card.deleted`	`deleteCard`	`card`	`trello.card`

Confluence Events

Confluence webhook setup is manual.

Event type	Native event	Subject	Source kinds
`confluence.page.created`	`page_created`	`page`	`confluence.space`
`confluence.page.updated`	`page_updated`	`page`	`confluence.space`
`confluence.page.deleted`	`page_removed`	`page`	`confluence.space`
`confluence.blog.created`	`blog_created`	`blog`	`confluence.space`
`confluence.blog.updated`	`blog_updated`	`blog`	`confluence.space`
`confluence.blog.deleted`	`blog_removed`	`blog`	`confluence.space`
`confluence.attachment.created`	`attachment_created`	`attachment`	`confluence.space`
`confluence.attachment.updated`	`attachment_updated`	`attachment`	`confluence.space`
`confluence.attachment.deleted`	`attachment_removed`	`attachment`	`confluence.space`

Notion Events

Notion webhook setup is manual.

Event type	Native event	Subject	Source kinds
`notion.page.created`	`page.created`	`page`	`notion.page_tree`
`notion.page.updated`	`page.updated`	`page`	`notion.page_tree`
`notion.page.deleted`	`page.deleted`	`page`	`notion.page_tree`
`notion.database.created`	`database.created`	`database`	`notion.page_tree`
`notion.database.updated`	`database.updated`	`database`	`notion.page_tree`
`notion.database.deleted`	`database.deleted`	`database`	`notion.page_tree`

SendGrid Events

SendGrid webhook setup is manual.

Event type	Native event	Subject	Source kinds
`sendgrid.email.delivered`	`delivered`	`email_message`	`sendgrid.contact_lists`, `sendgrid.templates`, `sendgrid.campaigns`
`sendgrid.email.bounced`	`bounce`	`email_message`	`sendgrid.contact_lists`, `sendgrid.templates`, `sendgrid.campaigns`
`sendgrid.email.opened`	`open`	`email_message`	`sendgrid.contact_lists`, `sendgrid.templates`, `sendgrid.campaigns`
`sendgrid.email.clicked`	`click`	`email_message`	`sendgrid.contact_lists`, `sendgrid.templates`, `sendgrid.campaigns`
`sendgrid.email.unsubscribed`	`unsubscribe`	`email_message`	`sendgrid.contact_lists`, `sendgrid.templates`, `sendgrid.campaigns`

MailJet Events

MailJet webhook setup is manual.

Event type	Native event	Subject	Source kinds
`mailjet.email.delivered`	`sent`	`email_message`	`mailjet.contact_lists`, `mailjet.templates`, `mailjet.campaigns`
`mailjet.email.bounced`	`bounce`	`email_message`	`mailjet.contact_lists`, `mailjet.templates`, `mailjet.campaigns`
`mailjet.email.opened`	`open`	`email_message`	`mailjet.contact_lists`, `mailjet.templates`, `mailjet.campaigns`
`mailjet.email.clicked`	`click`	`email_message`	`mailjet.contact_lists`, `mailjet.templates`, `mailjet.campaigns`
`mailjet.email.unsubscribed`	`unsub`	`email_message`	`mailjet.contact_lists`, `mailjet.templates`, `mailjet.campaigns`

Trigger Payload Context

Every event-triggered run receives normalized subject and event data:

Run field	Meaning
`provider`	Provider that produced the event.
`eventType`	Dawn event type.
`subjectKind`	Subject category, such as `pull_request`, `issue`, `work_item`, or `email_message`.
`subjectExternalId`	Provider subject ID or key.
`subjectTitle`	Human-readable title when available.
`subjectUrl`	Provider URL when available.
`triggerEvent`	Normalized JSON event body for the run.

Workflow prompts should refer to “the event subject” rather than hard-coding a PR number, issue key, or work item ID. Dawn passes that subject into the workflow run.