A report is sent to a webhook target only after a user action.
Webhooks & integrations
FairLix hands reports over to webhook targets in a controlled way.
FairLix is currently reduced to webhook and automation targets such as Make, Zapier or custom HTTPS endpoints. Native CRM integrations will be revisited only when customer demand and review effort are clear.
Current product state
Webhook / Make / Zapier
A reduced dataset is transferred only after active user approval.
Contact, company, summary, status and next step instead of an automatic full transcript.
Webhook connections can be saved, tested and disconnected again.
Webhook / Make / Zapier
FairLix sends a structured, reduced dataset to a stored HTTPS URL. Teams can trigger automations in Make, Zapier or internal systems without publishing or certifying a native CRM app.
Which data is sent?
Contact
Name, email, phone, position and company relation, if present in the report.
Company
Company name, website or domain for matching and assignment.
Report
Title, short summary, category, priority, lead/follow-up status, date, next step and FairLix reference.
Not automatic
Complete transcripts are not automatically transferred to external systems.
Privacy and responsibility
The handoff happens only after active approval. The user or business admin remains responsible for permissions, information obligations, legal basis and further processing in the target system.
Later CRM providers
Native CRM integrations are not part of the visible FairLix product at the moment. If customers ask for specific target systems, the matching OAuth, review and support paths will be verified separately before they are made visible again.