Docs

Integrations / Ticketing

Airtable

Airtable ticketing integration

Overview

The Airtable integration provides two-way ticket synchronization between Risotto and an Airtable base, for teams who run their helpdesk on Airtable instead of a traditional ITSM tool. When a ticket is created in Risotto, a matching record is created in your Airtable table โ€” and comments, assignee changes, and resolutions made in Airtable sync back to Risotto and Slack.

Prerequisites

Before connecting, make sure you have:

  1. An Airtable Enterprise personal access token with access to the target base and at least these scopes: data.records:read, data.records:write, schema.bases:read, and webhook:manage
  2. Your Base ID โ€” found in the Airtable API documentation for your base, or in the base URL
  3. A table in that base with these fields:
    • a single select field for the status, with an option for resolved tickets
    • a text field for the title
    • a text or User field each for the requester and the assignee
    • a long text or rich text field for the conversation log
    • an attachment field

Configuration

When connecting Airtable in Risotto, you'll provide:

FieldRequiredDescription
Personal Access TokenYesYour Airtable Enterprise token
Airtable Base IDYesThe base containing your ticket table
Airtable Table IDYesThe ID of the table Risotto should sync tickets into
Page Interface ID (Optional)NoPoint the Open in Airtable link at an interface page instead of the raw data table
Fields MappingYesMap Risotto's Status, Title, Requestor, Assignee, Conversation, and Attachments to fields in your table
ResolvedYesThe status option Risotto sets when a ticket is resolved or closed. Setting a record to this option in Airtable resolves the ticket
OpenNoThe status option Risotto sets when a ticket is open, in progress, or awaiting support
Waiting for ApprovalNoThe status option Risotto sets while a ticket awaits approval
Chat URLNoA URL field that gets a link to the request's chat thread
PriorityNoA single select field for the ticket's priority, with the option to use for each of Urgent, High, Medium, and Low
Default AssigneeNoAn email for a User-type Assignee field when the ticket is assigned to a bot instead of a person
Custom FieldNoSet a constant value on a text field for every ticket Risotto creates (e.g. a Queue field)
Comment DividerYesThe divider Risotto adds between comments in the conversation log

Setup Process

Step 1: Configure a Department

You need permission to change the department's settings: an Org Admin, a Manager, or a Supervisor of the department.

  1. Open your department

    In your Risotto dashboard, go to Settings. Under Departments, click a department, then click Ticket Sync.

  2. Add Airtable ticket sync

    Click Add ticket sync and select Airtable. Add ticket sync shows only while the department has no ticket sync: a department syncs with one ticketing system.

  3. Enter your connection details

    In the Configure Airtable for <department> dialog, enter the Personal Access Token, Airtable Base ID, and Airtable Table ID, and optionally a Page Interface ID. Then click Load table schema.

    Once the schema loads, the token, base, and table fields become read-only.

  4. Map your fields

    Under Fields Mapping, map Status, Title, Requestor, Assignee, Conversation, and Attachments to fields in your table. Each list shows only the fields of a type it accepts. After you pick the Status field, choose its option for Resolved, and optionally for Open and Waiting for Approval. Optionally, map Chat URL, Priority (with an option for each priority), a Default Assignee, and a Custom Field with its value.

    Fields are stored by ID, so renaming a field in Airtable later won't break the sync. Status and priority options are stored by name: if you rename one in Airtable, choose it again here.

  5. Save

    Enter a Comment Divider and click Save. Save turns on once every required field is filled in.

    Make sure External ticket sync enabled is on for the department. To change the mapping later, open the Connected menu on the Airtable card and click Configure....

Step 2: Test the Integration

Create a test ticket through Risotto and confirm a matching record appears in Airtable with the right fields populated. Then set the record's status to the option you mapped to Resolved and confirm the Risotto ticket resolves.

Comments and internal notes

When someone adds a comment to the conversation log in Airtable, Risotto adds it to the Risotto ticket and, if the ticket has one, to the ticket's thread in your agent channel. Risotto also posts it to the requester's Slack thread, unless the comment is an internal note.

A comment is an internal note when one of these is true:

  • The comment's author line contains (Internal). The author line is the line with the author's email address and the date, for example ivan@example.com (Internal) 9/22/2026 5:11pm. Lines above the author line, such as a status line, are ignored.
  • The text after the author line starts with ๐Ÿ”’ (or :lock:).

Risotto stores an internal note as an internal comment on the ticket. The requester does not see it.

Attachments

Screenshots and files shared in Slack upload to the record's attachment field in Airtable automatically.

Troubleshooting

422 errors when creating or updating a ticket

This usually means the Requestor or Assignee email doesn't match a user in your Airtable base's Enterprise directory โ€” Airtable can't put an unrecognized email into a User field. Confirm the person exists as an Airtable user, or adjust the default assignee.

If your Requestor or Assignee field is a single collaborator field, the person also has to be a collaborator on the base itself. When Airtable rejects a record for this reason, your Risotto admins receive a notification that names the user and field (for example, Cannot resolve the user โ€ฆ for field Requestor) instead of a generic 422 error. To fix it, add the user as a collaborator on the base, or map the field to a plain text field instead.

Connection rejected or webhook registration fails

Confirm the personal access token has the webhook:manage scope and access to the base. If Airtable refuses the token when Risotto registers the webhook, your Risotto admins receive an Airtable connection needs to be reconnected notification. Also confirm the token is an Enterprise token, not a Business-tier token โ€” the Requestor/Assignee User field lookup requires Enterprise API access.

Comments intermittently not syncing

Airtable's API occasionally returns temporary server errors during high load. Risotto retries automatically; if a comment is still missing after a few minutes, check the ticket for a sync error and try again.

Best Practices

  1. Use a dedicated Enterprise token: Generate the personal access token from a service account, not a personal one
  2. Set a default assignee for bot assignments: If your Assignee field is a User field, set a Default Assignee so tickets assigned to a bot still get an Airtable user
  3. Test with a small table first: Verify field mapping and the sync direction before rolling out to your full base

Something wrong or missing? Report an issue ยท View as Markdown