Use an approved view
Choose records intended for customer support, such as a public service catalog or product specifications.
Integrations Airtable
AirtablePlanned
AirtablePlannedAirtable records. Carefully scoped support context.
Plan an Airtable connector for selected tables and fields, separating public product knowledge from private customer records.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
Knowledge
What we’re planning to connect.
- 01Airtable
- 02Planned connection
- 03Message support
Select fields explicitly
Internal costs, staff notes and linked customer records should not travel with a public catalog by default.
Preserve record meaning
The proposed mapping must handle linked records, empty values and changes without combining unrelated customers.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Selected bases and tables
Allowlisted fields
Public versus private records
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Prepare a small catalog view and identify every field that is safe for customer answers.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Add a private field and a linked customer record, then verify neither appears in public retrieval.
Before you connect
Airtable integration questions
Can I connect Airtable to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Add a private field and a linked customer record, then verify neither appears in public retrieval.