Connect a provider
1
Confirm ownership
Use an external account and credentials that the organization has approved for this connection.
2
Open Integrations
Select the provider and enter the fields requested by Floral. Only administrators can manage the connection.
3
Test the connection
Save the configuration and check the status shown for the provider.
4
Review imported or synced data
Check a small, known set of records before relying on the connection for normal work.
webCRM
The webCRM form asks for WebCRM-token, CVR-feltnøgle, Ansvarlig bruger, and Mødehistorik i dage. Save with Gem WebCRM-forbindelse. Turn on Sync briefings to WebCRM when Floral should write each briefing as a completed activity. Approved meeting summaries always sync as meetings. Sync internal meetings is a separate switch. Follow the webCRM setup guide for the token, CVR field, company matching, and your first sync.Pipedrive
Enter CVR-feltnøgle before you connect. After the connection is active, Opret deal pr. referat is off until you turn it on. The default is a completed meeting activity with the summary and a Floral link. When the switch is on, you can choose Pipeline (valgfrit) for the Pipedrive pipeline that should receive the deal. Follow the Pipedrive setup guide to find the CVR field key, sign in, and check your first sync.Knack attendance
Follow the Knack setup guide for the required tables, fields, and a starter mapping. Organization administrators paste object and field keys into Knack mapping JSON.meetingAttendancePolicy controls who is written as attendees on the synced meeting:
noneskips attendees.syncwrites the calendar attendees.approver_onlywrites only the consultant who approved the summary.
approver_only with meetingAttendeesFieldKey. Look up that consultant in meetingAttendeesObjectKey and meetingAttendeesEmailFieldKey together, or both contact keys. Do not use employeesObjectKey for that lookup.
To create a child attendance record for the approving consultant’s employees id, set meetingAttendanceObjectKey, meetingAttendanceMeetingFieldKey, and meetingAttendancePersonFieldKey together. Also set employeesObjectKey and employeeEmailFieldKey together, or both contact keys as a fallback. Optional meetingAttendanceCompanyFieldKey and meetingAttendanceCreatedByFieldKey copy the company and consultant onto that row. Leave those keys unset to skip the join-object write.
