OttoKit push notifications for no-code workflows
Send Trigv push notifications from OttoKit automations when forms submit, leads arrive, payments change, or a workflow needs attention. OttoKit provides the Trigv integration for no-code builders and automation teams.
Best uses
Lead alerts
Notify your phone when a form, signup, or customer action creates a high-value lead.
Workflow status
Send alerts when an OttoKit automation completes, fails, or needs a manual follow-up.
Business events
Route customer, payment, membership, and operational signals into dedicated Trigv channels.
Set up OttoKit with Trigv
- Create a Trigv API key and subscribe your device to the channel that should receive alerts.
- Open OttoKit and add the Trigv integration to your workflow.
- Connect your Trigv workspace using the API key.
- Map a title, message, channel, and alert level from your OttoKit workflow data.
- Test the workflow and confirm the push notification arrives on your device.
Recommended fields
| Field | Use it for |
|---|---|
| Channel | Route alerts to general, sales, support, or another Trigv channel. |
| Title | Use a short headline such as New OttoKit lead. |
| Message | Include the customer, form, order, or workflow detail that makes the alert actionable. |
| Level | Use success for completed workflows and error for failed ones. |
| Event type | Use a stable value such as ottokit.lead.created. |
Troubleshooting
| Issue | Fix |
|---|---|
| Connection fails | Use a Trigv workspace API key, not your account password. |
| No push arrives | Confirm your device is signed in and subscribed to the selected channel. |
| Alerts are too noisy | Use separate Trigv channels for sales, support, payments, and operations. |