Core Concepts
Triggers & Actions
Triggers
Triggers are the entry point of every workflow. They listen for an event and fire the workflow when it occurs.
Webhook Trigger
The most flexible trigger. riogentix gives you a unique URL:
POST https://<tenant>.riogentix.com/webhook/<workflow-id>
Content-Type: application/json
{ "event": "order.created", "orderId": "12345" }
Authentication options:
- None (public — use only for low-risk workflows)
- Header Token (
X-Riogentix-Token) - Basic Auth
- HMAC signature verification
Schedule Trigger
Uses standard cron syntax:
| Expression | Meaning |
|---|---|
0 9 * * 1-5 | Weekdays at 9:00 AM |
*/15 * * * * | Every 15 minutes |
0 0 1 * * | First of each month |
Email Trigger (IMAP)
Polls a mailbox and fires once per new email. Available fields: from, to, subject, text, html, attachments.
Event Trigger
Subscribe to riogentix system events:
workflow.execution.failedcredential.expireduser.createdworkspace.member.added
Actions
Action nodes cause side effects in external systems.
HTTP Request Action
{
"method": "POST",
"url": "https://api.example.com/v1/users",
"headers": { "Authorization": "Bearer {{ $credentials.myApiKey }}" },
"body": { "email": "{{ $json.email }}" }
}
Features:
- Full control over method, headers, body, query params
- Supports form-data, JSON, raw body
- Automatic pagination with cursor/page expressions
- Built-in retry with exponential backoff
Send Email Action
Configure via SMTP credential or provider integrations (SendGrid, Mailgun, Postmark). Supports HTML templates with {{ }} variable interpolation.
Database Action
Supports PostgreSQL, MySQL, MSSQL, MongoDB, Redis, and SQLite.
INSERT INTO events (user_id, event, created_at)
VALUES ('{{ $json.userId }}', '{{ $json.event }}', NOW())