Skip to main content

Hey guys,

 

I’m trying to integrate Affinity and Airtable so that whenever I add a new company to an Affinity list, it creates/updates a record in Airtable. My problem is that when I try to map the fields, I don’t get all of the right field options showing from Affinity. The base, table, lookup field, etc. are all correct.

 

Has anyone had this issue? 

Hi ​@chalff 

For us to have more info, post screenshots showing how your Zap steps are outlined and configured in EDIT mode with the field mappings, and provide more details about what specific data points you are having issues with.


Thanks. My first step (below) is the Setup for an Affinity Trigger that hits whenever a New List Entry in created. It pulls from my Affinity Account. The account name is weird, but it is the right one.

 

Next, in Configuration it pulls from my Airtable - Affinity List. I test this step and see the List Entries I want. So no issues here. 

 

Where I have issues is the subsequent Trigger, Creating or Updating a Record In Airtable. Below you will see the Trigger Setup, which is fine. Further below in configuration s where I start to have issues. I can select the base, table, and lookup field that I need. I can even get one of the fields (Bank Name) correctly mapped. But all other fields which I would want to map my Affinity Fields to in Airtable do not show up in the drop down. Instead, it shows a bunch of things which are not fields in the Affinity list (last pic I have uploaded).

 

I’m wondering if this has something to do with the fields not being specific to the Affinity list? Not sure what else the issue could be. 

 

 


Hi ​@chalff 

There are some limitations to using the Zap action: Airtable - Create or Update Record

These cannot be computed fields and must be of the following field types:

  • number
  • text
  • long text
  • single select
  • multiple select
  • date

 

Instead, try these Zap steps:

  1. Trigger: Affinity - New List Entry
  2. Action: Airtable - Find Record
    1. Enable the checkbox to create record if not found
    2. So the step logic becomes find record else create record
  3. Action: Filter
    1. Check if found = true
    2. No point in updating a newly created record, only an existing found record
  4. Action: Airtable - Update Record
    1. Map the record ID from step 2

Hi ​@chalff,
 
We just wanted to see how everything is going with your Zap. Did Troy's recommendation get the job done? Feel free to reach out if you need further assistance with your Zap. We're glad to address any concerns and assist you.
 
We're looking forward to your response.


Reply