Question 1

How does Polytomic model Affinity lists and fields?

Accepted Answer

Lists are treated as first class rather than squeezed into the entity record. People and organizations have a root schema, and each list becomes its own schema identified by the entity type and list ID. Every list entry row carries the underlying entity ID plus a list entry ID that acts as the row identity. Custom fields are flattened into columns: entity level fields under their field ID, list specific fields under a field and list combination, and compound fields expose their subfields separately. A list row includes both the entity's own field values and that list's values, with other lists' values filtered out.

Question 2

Does Affinity sync incrementally?

Accepted Answer

There are two mechanisms and it depends on the object. Calls, emails, meetings, and notes support native timestamp filtered incremental reads through Affinity's v2 API. People, organizations, opportunities, lists, and notes can use optional webhook backed ingestion, which you enable on the connection and which covers creates, updates, deletes, field value changes, list entry changes, and organization merges. Rather than trusting partial webhook payloads, Polytomic refetches the affected record so you get a complete current snapshot. Without webhooks enabled, those core entities are read by full enumeration on each ETL run.

Question 3

What can Polytomic write back into Affinity?

Accepted Answer

People, organizations, and opportunities support create only, update only, and create or update, all requiring an identity. Notes can be created. Matching is flexible: people by Affinity ID or email, organizations by ID, name, or primary domain, and opportunities by ID or name. Importantly, matching is not fuzzy, Polytomic uses Affinity search and then verifies an exact match ignoring case and diacritics. Writing to a list will add an existing entity to that list in create or upsert mode, which is how reverse ETL from a data warehouse segment builds an Affinity list. There is no delete mode, no list creation, and no way to remove list membership.

Question 4

What happens when something is deleted in Affinity?

Accepted Answer

With webhook ingestion enabled, deletions of entities, list entries, and notes are captured as events and reflected in your destination. Without webhooks, Affinity's API gives no signal that a record was removed, so a deleted record simply stops appearing and your destination keeps the stale row until you resync. If deletion accuracy matters for your reporting, enabling webhooks is the answer, with a periodic full resync as a backstop since webhook delivery is never guaranteed.

Question 5

How does Polytomic handle Affinity's API limits?

Accepted Answer

Affinity enforces both per user and monthly organization quotas, which matters because they are easier to exhaust than most CRM APIs. Polytomic paces itself well below the ceiling, retries extensively with exponential backoff, and honors Affinity's reset headers. If the monthly organization quota is exhausted and the reset is more than an hour away, the sync fails immediately with a clear message rather than blocking for hours. Some read patterns are unavoidably expensive, particularly interaction date fields on people and organizations, so scope those to lists that actually need them.

Affinity CRM

Perfect pairings

Lists as first class tables

Webhook backed updates

Deep field coverage

Example workflows

What you can sync

From Affinity CRM

To Affinity CRM

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Affinity CRM in minutes

More integrations beyond Affinity CRM