You installed the CF7 to Airtable plugin, generated a token from your Airtable account, pasted it into the plugin settings, and now you are staring at an empty dropdown where your bases and tables should appear. The plugin says it connected but nothing loads.
This is exactly what one developer experienced and posted on the WordPress support forums. The fix was simple once the plugin author looked at the screenshots: the token was too short. It was either truncated when it was copied or the wrong type of token was used.
But there is more to this problem than just copy-paste errors. This post covers the full picture so you get your CF7 to Airtable integration working correctly the first time.
The Token Type Problem: Legacy API Key vs Personal Access Token
Airtable deprecated their legacy API keys in early 2024. If you have used Airtable for a while and have an old connection somewhere, you might have a legacy API key that looks like this:
keyXXXXXXXXXXXXXX
That format no longer works. Airtable now uses Personal Access Tokens (PATs). A correctly formatted PAT looks like this:
patXXXXXXXXXXXXXX.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
It starts with pat, has a 17-character identifier, a dot, and then a long 64-character string. The full token is much longer than the legacy API key. If the token you pasted into the plugin is short or does not start with pat, that is why your tables are not loading.
The Scope Problem: Token Has No Permission to Read Bases
Even with a correctly formatted PAT, your tables will still not appear if the token does not have the right scopes assigned to it.
When you create a Personal Access Token in Airtable, you choose which permissions it has. The minimum scopes needed for a CF7 plugin to list your bases and tables are:
-
data.records:writeso it can create new records from form submissions -
schema.bases:readso it can read the list of your bases and tables
If schema.bases:read is missing, the plugin authenticates successfully but when it tries to fetch the list of your bases to populate the dropdown, Airtable returns an empty or forbidden response. From the plugin's side it looks like there are no bases. From your side it looks like the integration is broken.
Go back to your Airtable token settings at airtable.com/create/tokens, find the token you are using, and check which scopes are assigned. Add schema.bases:read if it is missing.
The Access Problem: Token Cannot See the Right Bases
The third reason tables do not load is that the token's access is not set to include the base you want to use.
When creating a PAT, you choose which bases it can access. You can set it to "All current and future bases" or restrict it to specific bases. If you restricted it and the base you want to connect to was not included, the plugin will not be able to see it.
Check the access settings on your token and make sure the base you want appears in the list, or change the access to "All bases" if you want the plugin to show everything.
How to Generate a Token That Actually Works
Go to airtable.com/create/tokens and create a new token. Give it a descriptive name like "WordPress CF7 Integration" so you can find it easily later.
Under Scopes, add at minimum:
data.records:writeschema.bases:read
Under Access, either select "All current and future bases" or choose the specific base your CF7 form should write to.
Click Create Token and copy the full token immediately. Airtable only shows you the complete token once. If you close the screen without copying it, you will need to regenerate it. The token starts with pat and is quite long. Copy all of it.
Paste the complete token into the plugin settings. If the bases and tables now appear in the dropdown, the token is working correctly.
Testing the Token Before Connecting the Plugin
If you want to confirm your token is valid before touching the plugin settings, you can test it with a quick API call. Open your browser's address bar or use any API testing tool and call:
GET https://api.airtable.com/v0/meta/bases
Authorization: Bearer YOUR_PAT_TOKEN
If the token is valid and has the right scopes, you get back a JSON object listing your bases with their IDs and names. If you get a 401 or 403 response, the token has an issue with either its validity or its scopes.
The Alternative: Connect CF7 Directly to Airtable's API
Dedicated CF7 to Airtable plugins require a specific token format and scope setup that varies by plugin version and Airtable API changes. When Airtable updates something, the plugin may stop working until it is updated too.
Contact Form to API connects CF7 directly to Airtable's REST API endpoint. You configure the specific Airtable base URL, add your PAT as a Bearer authorization header, and map your CF7 fields to the Airtable column names. Because you are calling the API directly with the exact endpoint and field names, there is no middleware layer that can break when Airtable changes their token format.
Quick Checklist
If your tables are not loading in the CF7 Airtable plugin:
Check that your token starts with pat and is the full length. A short token or one starting with key will not work.
Check the token scopes include schema.bases:read and data.records:write.
Check the token access includes the base you want to use.
Regenerate the token if you are unsure whether you copied it completely the first time.
Test the token directly against api.airtable.com/v0/meta/bases to confirm it works before blaming the plugin
