What you can do
- Find accessible bases and tables, read records, and import contact details into your practice.
- Optional: add new leads to a table you choose, only after you turn on writes and confirm each one.
Know before you start
- An import is a copy into Aura, not continuous two-way contact syncing.
- Importing contacts does not send invitations. Review the contacts before taking a separate invitation action.
Connect step by step
You’ll need
- An Airtable account with access to the base you want to use.
- For contact imports, an Aura practitioner account and a table with a name plus an email or phone field.
Choose your contact table
In Airtable, note the base name, table name, and exact column names for name, email, and phone. Start with a small, clean sample.
Create a scoped token
Open Airtable’s token page using the link below. Create a personal access token with data.records:read and schema.bases:read. Add the specific base under access/resources. Your own Airtable account must also have access to it.
Save it in Aura
Open Connectors → Airtable → Connect. Paste the token into the password field and choose Save securely. Leave writes off for reading and importing. Never paste the token into a chat.
Check access before importing
Ask Aura to list the tables in your chosen base. Check that the expected table and contact columns appear. A saved connection alone does not prove that every base is accessible.
Import and review
Name the base, table, and contact columns in your request. Aura reads contact fields in pages of 20 and imports through its contact-review flow. Review added, duplicate, and failed counts; a partial page is not the whole table.
Check it works
Ask: “In Airtable, list the tables in my [base name] base. Do not change or import anything.” Then confirm the expected table appears.
This guide does not run a test or change your account. Use the connection screen or the suggested request to check access.
Try a first task
Replace bracketed details with your own. Copying an example does not submit it.
In Airtable, list the tables in my [base name] base. Do not change or import anything.
Import contacts from Airtable base [base name], table [table name]. Use [name column], [email column], and [phone column]. Process every page, report added, duplicate, and failed counts, and do not send invitations.
If something gets stuck
My base or table is missing
Check both the token’s selected resources and your Airtable account’s access. Ensure schema.bases:read is included. Reconnect with a corrected token if needed.
Records appear, but contacts do not import
Use the exact column names. Each contact needs a usable email or phone. Formula, lookup, or multiple-value columns may need a plain-text contact column. Review failed rows before retrying.
The import stopped or the browser closed
Open Clients first and review what was saved. Return to the conversation and ask Aura to check the prior import result before continuing. Existing duplicate checks help, but changed email or phone details can represent a different record.
I want Aura to create Airtable records
Add data.records:write to the token for the selected base, then enable confirmed writes in Aura. Importing contacts from Airtable into Aura does not require Airtable write access.
Aura says I’m out of AI credits
Open Account & billing to check your balance and reset. If a task stopped, review completed actions before retrying. Provider limits or paid provider credits are separate from Aura’s balance.
Administrator setup is required
Contact Aura support with the service name. Re-entering your credentials will not fix a service that is unavailable on Aura.
Remove access
Choose Disconnect on the Airtable connection in Aura. Revoke the token in Airtable if you no longer use it elsewhere. Disconnecting does not delete contacts already imported into Aura.
Provider references
Provider screens can change. These official pages provide the latest provider-specific steps.