VeritableRollSALESFORCE + VERITABLEROLL
Membership status connected to Salesforce.
Synchronise selected contacts, organisations and renewal status with explicit field mappings and stable source identifiers.
Implemented and contract-tested. Production activation requires an approved Salesforce instance, connected app, object mapping and an authorised reconciliation test.
What the connector covers
- Upsert mapped contacts using a stable VeritableRoll external identifier.
- Map selected organisation and renewal-status fields for the agreed operating workflow.
- Restrict the destination instance and retain provider identifiers for reconciliation.
- Keep renewal evidence, approval and issuance controlled inside VeritableRoll unless an additional field is explicitly approved.
Data exchanged
The mapping is agreed per organisation. A typical scope contains member name, approved contact details, source member reference, organisation reference and current renewal status. Unmapped evidence and restricted branch data are not sent.
Activation and acceptance
- Approve the Salesforce instance, connected app, objects, fields and direction.
- Exercise representative contacts including a retry and a changed status.
- Reconcile source identifiers, permissions, removals and disconnect behaviour before scheduled use.