Custom Webhook

For tools without a native Finseo integration, use the universal webhook endpoint. POST any JSON payload to your project specific URL. Finseo auto detects known formats (HubSpot, Salesforce, Typeform, Jotform, Pipedrive, Attio) or accepts raw JSON with explicit fields. The most flexible attribution input mechanism in Finseo.

1. 01

   Custom CRM integration

   For homegrown or niche CRMs without native webhook support, build a custom integration that POSTs lead and deal data to the Finseo webhook endpoint.

2. 02

   Internal application tracking

   For internal apps that capture user signups, demos, or qualifications, POST events to Finseo for centralized AI attribution reporting.

3. 03

   Backend trigger

   Trigger attribution events from your backend (e.g. on stripe charge succeeded, on user upgrade) by POSTing to the Finseo webhook with the AI source from cookies or session data.

4. 04

   Multi-source consolidation

   Consolidate attribution data from multiple sources (form, CRM, payment) into one webhook with enriched metadata before sending to Finseo.

5. 05

   Migration from other tools

   Backfill historical attribution data from spreadsheets, databases, or legacy systems by POSTing to the Finseo webhook in a script.

Every team has at least one tool without a native Finseo integration. The custom webhook is the escape hatch that ensures Finseo can ingest attribution data from anything. POST raw JSON, structured payloads, or known formats. Finseo handles the parsing. This makes Finseo the centralized attribution layer for your full stack, not just the integrations we have built natively.

1. 01

   Get your Finseo webhook URL

   In Finseo, click Connect on the Custom Webhook integration card to reveal your project specific webhook URL.

2. 02

   Decide on payload format

   For explicit control, use { channelId: "ai_chatgpt", respondentEmail: "[email protected]", dealValue: 1000 }. For auto detection, send any JSON with a field containing attribution keywords.

3. 03

   POST to the URL

   From your application, script, or third party tool, POST a JSON payload to the webhook URL. Add HTTP header Content-Type: application/json.

4. 04

   Optional: add HMAC signature

   For security, configure an HMAC SHA256 signing key in Finseo Attribution settings. Sign the payload and include the signature in the X-Finseo-Signature header. Finseo verifies the signature before processing.

5. 05

   Verify in dashboard

   Submit a test payload. Check the Finseo Attribution dashboard within 10 seconds. Check the Finseo logs (Settings, then Logs) if data does not appear.

When should I use the custom webhook instead of a native integration?

Use the custom webhook when your source tool does not have a native Finseo integration, when you need transformation logic before sending data, when you want to consolidate multiple sources into one webhook, or when you are building a custom backend trigger.

Use the custom webhook when your source tool does not have a native Finseo integration, when you need transformation logic before sending data, when you want to consolidate multiple sources into one webhook, or when you are building a custom backend trigger.

What is the minimum required payload?

The minimum is { "channelId": "ai_chatgpt" } where channelId is one of the supported AI source IDs (ai_chatgpt, ai_perplexity, ai_claude, ai_gemini, ai_copilot). Optionally add respondentEmail, respondentName, dealValue, dealCurrency, formId, pageUrl, metadata.

The minimum is { "channelId": "ai_chatgpt" } where channelId is one of the supported AI source IDs (ai_chatgpt, ai_perplexity, ai_claude, ai_gemini, ai_copilot). Optionally add respondentEmail, respondentName, dealValue, dealCurrency, formId, pageUrl, metadata.

Does Finseo auto detect known formats?

Yes. Finseo auto detects payloads from HubSpot, Salesforce, Typeform, Jotform, Pipedrive, Attio, Calendly, and Intercom. Just POST the raw payload from those tools and Finseo extracts the relevant fields. For unknown formats, send explicit fields.

Yes. Finseo auto detects payloads from HubSpot, Salesforce, Typeform, Jotform, Pipedrive, Attio, Calendly, and Intercom. Just POST the raw payload from those tools and Finseo extracts the relevant fields. For unknown formats, send explicit fields.

Can I sign webhooks for security?

Yes. Configure an HMAC SHA256 signing key in Finseo Attribution settings. Sign each request payload with the key and include the signature in the X-Finseo-Signature header. Finseo verifies every signature and rejects tampered requests with HTTP 401.

Yes. Configure an HMAC SHA256 signing key in Finseo Attribution settings. Sign each request payload with the key and include the signature in the X-Finseo-Signature header. Finseo verifies every signature and rejects tampered requests with HTTP 401.

What is the webhook rate limit?

100 requests per second per project, with burst capacity to 500 per second. For higher volumes, contact us. Most teams send fewer than 100 events per minute, so the limits are generous for typical use cases.

100 requests per second per project, with burst capacity to 500 per second. For higher volumes, contact us. Most teams send fewer than 100 events per minute, so the limits are generous for typical use cases.

How do I test the webhook?

Use the curl example from the integration card, or test with Postman. Set Method POST, URL to your project webhook, header Content-Type: application/json, body to a test JSON payload. Check the Finseo dashboard within 10 seconds.

Use the curl example from the integration card, or test with Postman. Set Method POST, URL to your project webhook, header Content-Type: application/json, body to a test JSON payload. Check the Finseo dashboard within 10 seconds.

Can I send historical attribution data?

Yes. POST historical data with a custom timestamp field (ISO 8601 format) to backfill. Finseo accepts events up to 90 days old by default. For older backfills, contact us.

Yes. POST historical data with a custom timestamp field (ISO 8601 format) to backfill. Finseo accepts events up to 90 days old by default. For older backfills, contact us.

What if the webhook fails?

Finseo returns HTTP 200 on success. On failure (4xx or 5xx), implement retry logic in your sender (exponential backoff is recommended). Common failure causes include invalid JSON, missing channelId, or rate limit exceeded. Check the Finseo logs for details.

Finseo returns HTTP 200 on success. On failure (4xx or 5xx), implement retry logic in your sender (exponential backoff is recommended). Common failure causes include invalid JSON, missing channelId, or rate limit exceeded. Check the Finseo logs for details.