GitHub Actions Notifications | Trigv Integrations

Best uses

Failed builds

Alert the right channel when a CI job breaks on main, a pull request, or a scheduled workflow.

Deployments

Notify your phone when production, staging, or preview deployments complete successfully.

Release jobs

Track package publishes, migrations, nightly jobs, and manual release workflows without watching GitHub.

Set up the action

Create a Trigv API key and subscribe your phone to a channel such as ci.
Add the key as a repository secret named TRIGV_API_KEY.
Add the Trigv action near the end of the job you want to monitor.
Run the workflow and confirm the push arrives on your phone.

Notify on failure

Use this after your test or deploy steps so GitHub only sends the notification when the job fails.

Code

- name: Notify Trigv on failure
	if: failure()
	uses: Trigv/[email protected]
	with:
		api-key: ${{ secrets.TRIGV_API_KEY }}
		channel: ci
		title: GitHub Actions workflow failed
		level: error
		event-type: github.workflow.failed

Notify on deploy success

Change the title, channel, and event type for production deploy alerts.

Code

- name: Notify Trigv on deploy
	if: success()
	uses: Trigv/[email protected]
	with:
		api-key: ${{ secrets.TRIGV_API_KEY }}
		channel: deploys
		title: Production deploy completed
		level: success
		event-type: github.deploy.succeeded
		idempotency-key: ${{ github.run_id }}-deploy

Useful inputs

Input	Use it for
`api-key`	Workspace API key stored in `secrets.TRIGV_API_KEY`.
`channel`	Route CI, deploy, or release notifications to the right Trigv channel.
`title`	Short notification headline shown on the device.
`description`	Optional message. If omitted, the action includes GitHub workflow context.
`level`	`info`, `success`, `warning`, or `error`.
`event-type`	Stable event name such as `github.deploy.succeeded`.
`delivery-urgency`	Use `time_sensitive` for alerts that should break through allowed Focus settings.
`idempotency-key`	Deduplicate retries from the same workflow run.

Troubleshooting

Issue	Fix
No push arrives	Confirm the phone is signed in and subscribed to the channel used by the workflow.
`401` from Trigv	Regenerate the workspace API key and update the GitHub secret.
Duplicate alerts	Add an `idempotency-key` based on `github.run_id` or another stable run value.

All integrations Browse live, beta, and planned Trigv integrations. Webhooks Send any HTTP POST request to Trigv with the event API. SDKs Use Trigv from app code, scripts, CLIs, and AI agents.