Webhooks
Webhooks enable real-time data synchronization. When a record changes in a connected system, a webhook notifies FluxCascade immediately, triggering an instant sync for that specific record.
How Webhooks Work
1. User updates a contact in HubSpot
2. HubSpot sends a webhook to FluxCascade
3. FluxCascade receives the notification
4. The affected mapping(s) are identified
5. The specific record is synced to target system(s)
6. Sync completes in seconds
Benefits of Webhooks
| Benefit | Description |
|---|---|
| Real-time sync | Changes sync in seconds, not hours |
| Efficient | Only syncs changed records, not entire datasets |
| Lower API usage | No need to poll for changes |
| Immediate feedback | Users see synced data right away |
Webhook Support by Platform
| Platform | Webhook Support | Supported Events |
|---|---|---|
| HubSpot | ✅ Full support | Contact, Company, Deal create/update/delete |
| Jobber | ✅ Full support | Client, Job, Quote create/update |
| Pipedrive | ✅ Full support | Person, Organization, Deal create/update/delete |
| Salesforce | 🧪 Coming soon | Platform Events (beta) |
Enabling Webhooks
Automatic Registration
FluxCascade automatically registers webhooks when you enable real-time sync:
- Go to Mappings
- Open your mapping
- Click Settings
- Enable Real-time Sync
- Save
FluxCascade will:
- Register webhook subscriptions with the source system
- Configure the necessary event types
- Start listening for changes
Verifying Registration
After enabling, check the connection status:
- Go to Connections
- Click on the connection
- Look for Webhooks section
- Verify webhooks are Active
Webhook Events
Inbound Webhooks (From External Systems)
When external systems notify FluxCascade of changes:
| Event Type | Description | Action |
|---|---|---|
create | New record created | Create in target system |
update | Existing record modified | Update in target system |
delete | Record deleted | Archive or delete in target (configurable) |
merge | Records merged | Update references in target |
Outbound Webhooks (To Your Systems)
FluxCascade can also send webhooks to your own endpoints:
- Go to Settings → Webhooks
- Click Add Endpoint
- Enter your endpoint URL
- Select events to subscribe to
- Save
Use outbound webhooks to:
- Trigger custom workflows
- Update internal dashboards
- Log to external systems
- Send notifications
Viewing Webhook Activity
Webhook Deliveries
Go to Settings → Webhooks → Deliveries to see:
- Recent webhook events received
- Outbound webhook attempts
- Delivery status (success/failed)
- Payload preview
Sync Logs
Webhook-triggered syncs are marked in sync logs:
Trigger: Webhook
Event: contact.update
Record: john@example.com
Source: HubSpot
Webhook Security
Signature Verification
FluxCascade verifies webhook signatures to ensure authenticity:
- HubSpot: X-HubSpot-Signature header verification
- Jobber: Signature header validation
- Pipedrive: Webhook secret verification
Invalid signatures are rejected and logged.
HTTPS Only
All webhook endpoints use HTTPS:
- Data encrypted in transit
- TLS 1.2 or higher required
- Certificates validated
Secret Keys
For outbound webhooks, FluxCascade includes a secret:
X-FluxCascade-Signature: sha256=abc123...
Your endpoint should verify this signature.
Retry Logic
When webhook processing fails:
Inbound Webhooks
FluxCascade retries failed webhook processing:
- Immediate retry
- Retry after 1 minute
- Retry after 5 minutes
- Retry after 30 minutes
- Mark as failed, log error
Outbound Webhooks
For your endpoints:
- Retry after 1 minute
- Retry after 5 minutes
- Retry after 15 minutes
- Retry after 1 hour
- Retry after 4 hours
- Mark as failed
Failed webhooks can be manually retried from the deliveries page.
Best Practices
1. Combine with Scheduled Syncs
Webhooks are fast but not 100% reliable. Use scheduled syncs as backup:
- Webhooks: Handle real-time changes
- Hourly sync: Catch anything webhooks missed
2. Monitor Delivery Rates
Check the webhooks dashboard regularly for:
- Failed deliveries
- Unusual patterns
- Connectivity issues
3. Keep Endpoints Fast
For outbound webhooks, your endpoint should:
- Respond within 30 seconds
- Return 200 status immediately
- Process asynchronously if needed
4. Handle Duplicates
Webhooks may occasionally be delivered multiple times. Your systems should:
- Use idempotent operations
- Check if change already applied
- Track webhook IDs
Troubleshooting
Webhooks Not Triggering Syncs
Check:
- Is real-time sync enabled on the mapping?
- Is the connection active?
- Are webhooks registered (check connection details)?
- Is the record type included in the mapping?
Delayed Webhook Processing
Possible causes:
- High webhook volume
- Target system rate limits
- Processing queue backlog
Solutions:
- Check system status
- Review rate limit usage
- Contact support for high volume
Missing Webhook Events
Possible causes:
- Webhook not registered for that event type
- Event filtered out by source system
- Webhook delivery failed
Check:
- Webhook event subscriptions
- Source system webhook logs
- FluxCascade webhook deliveries page
Next Steps
- Scheduling – Configure backup scheduled syncs
- Error Handling – Handle webhook failures
- API Webhooks – Programmatic webhook management