People, orgs and lists
List targets create membership when it is missing.
Sync MySQL to Affinity with Polytomic and keep the relationship CRM fed from your own records. Aggregate before reverse ETL writes, because Affinity charges per field value rather than per record, and a wide model costs far more API calls than a narrow one.
List targets create membership when it is missing.
Small jobs and a request ceiling to respect quotas.
SELECT on the database is the whole requirement.
Polytomic is bi-directional by default, so you can move data the other way just as easily.
Affinity CRM to MySQL
Jonathan Krangel
VP Global Head of Revenue Operations
“Polytomic handles so many ETL and sync jobs at Cursor. They are a true partner to us.”
Follow these simple steps to connect MySQL with Affinity CRM in minutes
Connect MySQL
Connect Affinity CRM
Create sync
Enable sync
Connect MySQL to Polytomic with host, port, database, and credentials.
Connect Affinity to Polytomic with an API key, ideally from a dedicated Affinity user.
Sync data in either direction between MySQL and Affinity CRM. Choose the source data and destination objects for the direction you need.
Map the fields, choose the sync schedule and behavior, then save and enable the sync.
Get answers to common questions about the integration process
Sync data in either direction between MySQL and Affinity CRM.
Use both integrations' source and destination capabilities in one managed sync workflow.
Enterprise encryption and security protocols ensure your data remains protected.
Get up and running in minutes with our step-by-step integration guide.