Why does using a specific update trigger in Airtable cause a 'Field "FollowedSince" does not exist' error?

It appears that n8n is reporting an error because the field name referenced in your trigger is “FollowedSince” instead of “FollowingSince.” The error:

ERROR: The Field "FollowedSince" does not exist.

suggests that there’s a mismatch between the actual column name in your database (or the field available in your workflow) and the name you’ve configured for the trigger.

What to Check

1. Field Name Accuracy
   Verify that the field name in your configuration exactly matches the field in your data. In your case, if the actual last-updated field is named “FollowingSince,” then ensure the trigger is set to use that exact name. Pay close attention to case sensitivity and spelling.

2. Configuration Consistency
   Since you mentioned that using the last-updated trigger as a global field works fine, it suggests that the underlying mechanism is functioning properly—only the custom field setting is causing the issue. Double-check that in the custom configuration you haven’t inadvertently introduced a typo (for example, “FollowedSince” instead of “FollowingSince”).

3. Environment Considerations
   Given that you’re running n8n in a Docker container on Ubuntu 22.04, ensure that there are no caching issues. Sometimes configuration changes may not take effect immediately, so it might help to restart the container after you make adjustments.

Next Steps

• Open your trigger configuration and update the field name from “FollowedSince” to “FollowingSince.”
• Save your configuration and restart the workflow (or the n8n instance) if necessary.
• Test the trigger again to see if the error is resolved.

Making sure your custom field trigger has the correct spelling and capitalization should resolve the error. Let us know if you encounter any other issues!