ConnectedAutomation
Keep the introduction and the next system connected.
Use a configured external workflow to send selected intake details to your CRM and retain a job reference.
A complete worked example
Take a qualified intake into an existing CRM process.
The team has a Fermium intake table and an authorized external workflow that can create CRM records. It needs a deliberate field mapping.
Fictional project and sample data. This preview does not submit, publish, or change access.
Authorized CRM workflow · illustrative result
A lead that keeps its source context
Sample mapping for a separately configured CRM workflow.
- Fermium source
- Submission R31 · jamie@example.com · Acorn
- Selected fields
- Contact email, company, project interest
- CRM correlation
- Store R31 as the external reference
How to verify the result
The external service holds the CRM credential, applies its duplicate check, and reports whether it created or updated the record. Fermium's delivery result and the CRM's outcome are separate evidence.
What the recipient can access
The selected contact fields and the correlation identifier.
Kept out of this handoff
Unselected answers, internal assessment, and integration credentials.
How it runs
- Choose the permitted dataMap the required fields and identify the receiver authorized to process them.
- Configure the receiverSet up CRM credentials and duplicate handling in the external service.
- Verify the full handoffTest with synthetic data and inspect both Fermium delivery and downstream run status.
- You getA traceable handoff between the saved submission and the downstream CRM operation.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Plan and configure a handoff from [intake table] to [authorized CRM workflow]. Send only [selected fields]. Keep credentials in the external service’s secret storage, use the submission ID to prevent duplicates, and verify the flow with synthetic data before handling real records.
What this workflow needs
Requires an external workflow service, supported CRM API, permissions, and webhook entitlement. File references need a separately authorized fetch or transfer. A successful delivery is not proof of a CRM update.
Where do integration credentials live?
For this workflow, configure them in the external system. Fermium’s general workspace secrets manager remains future work.