Notifications & Webhooks
FrankieOne provides real-time notifications through webhooks to keep your systems updated about important events and changes.
To set up webhooks, have your designated contact email help@frankieone.com. You can configure endpoint collections for:
- Workflow execution completion
Notification Triggers
Triggered when a workflow execution completes.
Webhook Structure
Endpoint Format
FrankieOne appends the requestID
to your configured webhook endpoint:
Payload Examples
Handling Notifications
Receive the Webhook
Your endpoint should respond with a 200 or 202 HTTP status code to acknowledge receipt. If your endpoint returns a 5xx or 4xx status code (other than 400), the system retries delivery for a configurable amount of times over a period of time. The webhook will not be disabled however. If your endpoint returns a 400 status code, the message will not attempt retry.
Additional Security (JWT Authentication)
We secure notification payloads through HTTPS and firewall IP whitelisting. You can also sign your requests with JSON Web Tokens to add an additional layer of security and verify message validity. Contact support to enable JWT verification for your account.
JWT Structure
Security Features
- RSA-4096 bit private key encryption
- Customer-specific public key for verification
- HTTPS with secure algorithms
- IP whitelisting
Retry Mechanism
When webhook delivery fails to more than half of the configured endpoints:
- The system retries delivery every 15 minutes, with up to 50 retries.
- If all 50 retries fail, the message moves to a Dead Letter Queue (DLQ) and notifies our support team