Make scenario alerts with Trigv push notifications
Send Trigv push notifications from Make scenarios when an automation finishes, fails, or produces a result worth seeing immediately. Until native Make app support is ready, use the HTTP module to call the Trigv event API.
Best uses
Scenario results
Notify when a CRM sync, spreadsheet import, form workflow, or scheduled scenario completes.
Failure alerts
Send errors to a dedicated Trigv channel so failed scenarios do not disappear in email.
Business signals
Push high-value events such as new leads, invoices, customer updates, and operational handoffs.
Set up the HTTP module
- Create a Trigv API key and subscribe your device to a channel such as
automations. - Open the Make scenario you want to monitor.
- Add an HTTP module where the notification should run.
- Configure a POST request to the Trigv event API and map values from earlier modules.
HTTP module settings
| Field | Value |
|---|---|
| Method | POST |
| URL | https://api.trigv.com/api/v1/events |
| Headers | Authorization: Bearer trgv_YOUR_KEY and Content-Type: application/json. |
| Body type | Raw JSON |
JSON body example
Code
{
"channel": "automations",
"title": "Make scenario completed",
"description": "{{1.email}} synced to the CRM",
"level": "success",
"event_type": "make.scenario.completed"
}Use error handlers
Add a Make error handler route when failed scenarios should send a separate alert.
Code
{
"channel": "automations",
"title": "Make scenario failed",
"description": "{{error.message}}",
"level": "error",
"event_type": "make.scenario.failed"
}Troubleshooting
| Issue | Fix |
|---|---|
401 response | Check the bearer token and keep it in a Make connection or variable. |
422 response | Make sure channel and title are present in the JSON body. |
| No push arrives | Confirm the Trigv app is installed and subscribed to the selected channel. |