n8n push notifications with the HTTP Request node

Send Trigv push notifications from n8n workflows when automations finish, fail, or need human attention. Until a native Trigv node is available, the HTTP Request node gives you the same event API.

n8n to Trigv

Best uses

Set up the HTTP Request node

1. Create a Trigv API key and subscribe your device to a channel such as automations.
2. Add an HTTP Request node after the workflow step you want to monitor.
3. Store the Trigv key in n8n credentials as an Authorization header.
4. Send a JSON body to the Trigv event API and test the workflow.

HTTP Request settings

JSON body example

Use n8n expressions to include values from earlier nodes.

{
	"channel": "automations",
	"title": "n8n workflow completed",
	"description": "{{ $json.message || 'Workflow finished successfully' }}",
	"level": "success",
	"event_type": "n8n.workflow.completed"
}

Error workflow example

Create a separate workflow with an Error Trigger, then add the same HTTP Request node.

{
	"channel": "automations",
	"title": "n8n workflow failed",
	"description": "{{ $json.execution.error.message }}",
	"level": "error",
	"event_type": "n8n.workflow.failed"
}

Troubleshooting