Affinity

Supported Tables

Tables	Status
People	✅ Supported
Organizations	✅ Supported
Opportunities	✅ Supported
Notes	✅ Supported
Lists	✅ Supported

Full Records vs. Shallow Records

Unless you are on Affinity's Enterprise plan, Affinity has significant API limitations which limits our ability to sync all records. To work around this, Whalesync groups your records into two categories:

• Records you care about (full records)

• Records you don't care about (shallow records)

Affinity API limits

Affinity has the following API quota limits on its plans:

• Starter = none

• Premium = 100,000 calls/mo

• Enterprise = unlimited

Difference between full records and shallow records

Full records include every field you want to sync:

Shallow records only include the display name and email address (if applicable):

How to sync full records

By default, Whalesync will sync records as shallow records. If you want to fully sync a group of records you must:

1. Add them to at least one list

2. Select to fully sync that list on the table mapping screen

Open table settings on the table mapping screen

Add the lists you want to fully sync

List-specific Fields

Affinity lets you add list-specific fields that only appear on specific lists:

Example of adding a list-specific field

List-specific fields show up in Whalesync as available fields to map with a prefix of the list like so:

Example of a list-specific Amount field on the "Pitch Requests" list

Affinity Note Limitations

Creating vs. editing

If you map the "Notes" table and intend to author notes in another tool such as Airtable or Notion, there's a limitation you should be aware of. When creating a brand new note in Affinity, Whalesync is able to set all the note's properties: its contents and which people/organizations/opportunities it's associated with.

However, when editing a note, Whalesync can only modify the contents of the note. It cannot change the people/organizations/opportunities it's associated with.

Therefore we recommend setting a long sync delay on the "Notes" table mapping such that Whalesync only creates notes in Affinity once you've had the chance to set the appropriate references.

Edit mapping options for the "Notes" table

Set a long delay on the source of the notes

Notes and rich text

Notes in Affinity are usually stored as rich text. Under the hood, Affinity's internal representation of notes is Markdown, a simple formatting language. When you create notes within Affinity's UI, Whalesync sees those notes as being formatted in Markdown. You can map the contents of notes to a rich text field in tool such as Airtable and the formatting will correctly be synced.

However, due to a bug in the Affinity API, Whalesync is only able to edit notes in Affinity as plain text. When you create rich text notes in another tool and they're synced to Affinity, they will show up with the raw Markdown formatting like this:

Hello World!
This is **bold**, _italic_, ~~strikethrough~~, and `code`.
Here is a [link](https://en.wikipedia.org/wiki/Whale).