Overview
Webhooks let external systems receive real-time notifications when events happen in your Tryno community. Use them to sync data, trigger automations, or integrate with your existing tools.
Available events
| Event | Description |
|---|
member.joined | A new member joined the community |
member.left | A member left the community |
post.created | A new post was published |
post.deleted | A post was removed |
payment.completed | A payment was confirmed |
payment.refunded | A refund was processed |
challenge.enrolled | A member enrolled in a challenge |
challenge.completed | A member completed a challenge |
event.registered | A member registered for an event |
event.checked_in | A member checked in at an event |
Configuration
Go to Settings
Navigate to Admin > Settings > Webhooks.
Add your endpoint URL
Enter the HTTPS URL where you want to receive webhook payloads.
Select events
Choose which events should trigger a notification to your endpoint.
Save and test
Save the configuration and click Test to send a sample payload to your endpoint.
All webhooks follow a consistent JSON structure:
{
"event": "member.joined",
"timestamp": "2026-01-15T10:30:00Z",
"data": {
"community_id": "uuid",
"user_id": "uuid",
"metadata": {}
}
}
Security
Each webhook request includes an X-Tryno-Signature header containing an HMAC-SHA256 signature. Use your webhook secret (provided when you create the endpoint) to verify that the request genuinely came from Tryno.
Always verify the X-Tryno-Signature header before processing a webhook payload. This prevents malicious actors from sending fake events to your endpoint.
Retry policy
If your endpoint returns an error (HTTP status >= 400), Tryno retries the delivery:
| Attempt | Delay |
|---|
| 1st retry | Immediate |
| 2nd retry | 1 minute |
| 3rd retry | 5 minutes |
| 4th retry | 30 minutes |
After 4 consecutive failures, the webhook is automatically disabled. You can re-enable it from the settings page after resolving the issue.