Solutions by app
Airtable: Sync your bases to every system your team depends on
Airtable organizes operational data in bases and tables that teams use to manage everything from product roadmaps and campaign plans to hiring pipelines and asset libraries. Tray connects Airtable so record changes trigger workflows across your stack, and agents can read, create, and update records with context from every connected system.
Automations
Integrations
Agents
Use cases
Airtable + Tray
Airtable is where operational data lives: bases and tables built to match how your teams actually work, records capturing the state of projects, assets, campaigns, and requests, and views and linked records keeping everything connected within a base. What it doesn't do is act outside that base when something changes: it won't update a CRM record when a deal stage changes in your pipeline tracker, create a ticket when a bug is logged in your product base, sync a finalized asset to your DAM, or notify finance when a budget record is updated.
Tray bridges the gap, turning record events in Airtable into multi-step workflows that read from your bases, apply logic, and write to every system that needs to respond.
See how different teams use Tray to take action from Airtable.
What you can do with Tray
Operations
Operations
If you work in operations, these are common ways teams use Tray with Airtable to connect operational records to the tools and processes that keep your business running.
- Sync approved records to downstream systems: When a record in your Airtable ops base reaches an approved status, push the data to your ERP, billing platform, or project management tool automatically
- Trigger notifications from record updates: When key fields in an operational base change, notify the owning team via Slack or email without manual intervention
- Backfill and sync records from external systems: Pull data from connected business tools on a schedule and create or update records in Airtable to keep your operational base current
Marketing
Marketing
If you work in marketing, these are common ways teams use Tray with Airtable to connect campaign and content records to the platforms that publish and track them.
- Push approved content to publishing platforms: When a content record reaches a published status in your Airtable content calendar, trigger a workflow to publish or schedule it in your CMS or social platform
- Sync campaign records to your MAP: When a campaign record is created or updated in Airtable, create or update the corresponding campaign in your marketing automation platform
- Pull campaign performance back into Airtable: Run scheduled workflows to retrieve performance metrics from your analytics tools and update the matching campaign records in Airtable for team visibility
Product
Product
If you work in product, these are common ways teams use Tray with Airtable to connect product planning records to engineering tools and stakeholder workflows.
- Create issues from feature records: When a feature or bug record reaches a ready state in your product base, create a linked issue in your engineering tool with record context and field values mapped across
- Sync roadmap status to stakeholder tools: When a roadmap record is updated in Airtable, push the status change to your project management tool or stakeholder dashboard automatically
- Pull sprint and release data into Airtable: Run scheduled workflows to sync issue status and release data from your engineering tools back into your Airtable product base for unified visibility
Revenue operations
Revenue operations
If you work in revenue operations, these are common ways teams use Tray with Airtable to connect deal tracking and account records to your CRM and reporting tools.
- Sync pipeline records to your CRM: When a deal or account record is created or updated in your Airtable pipeline tracker, create or update the matching record in your CRM to keep both systems consistent
- Trigger approval workflows from record status changes: When a contract or pricing record reaches a review status in Airtable, route an approval request to the right stakeholder and update the record when approved
- Export revenue records for reporting: Pull deal and account records from Airtable on a schedule and push them to your data warehouse or BI tool for pipeline and revenue reporting
Engineering
Engineering
If you work in engineering, these are common ways teams use Tray with Airtable to connect technical tracking bases to your development and incident workflows.
- Create Airtable records from engineering events: When a deployment, incident, or bug is logged in your engineering tools, create a corresponding record in your Airtable tracking base automatically
- Sync issue status back to Airtable records: When a linked issue is resolved or updated in your project management tool, update the matching Airtable record so your tracking base stays current
- Push environment and release data to Airtable: Write deployment metadata and release notes into Airtable records so non-engineering teams have visibility into what shipped and when
IT
IT
If you work in IT, these are common ways teams use Tray with Airtable to connect access tracking, asset records, and onboarding bases to your identity and operations tools.
- Automate onboarding record creation: When a new hire is added in your HR system, create the corresponding record in your Airtable onboarding base and trigger downstream provisioning workflows
- Sync asset records to your ITSM: When an asset record is created or updated in Airtable, push the change to your ITSM platform to keep your configuration and asset inventory consistent
- Deprovision access from offboarding records: When an employee's record is marked as departed in Airtable, trigger access revocation workflows in your identity provider automatically
Automations
Automations with Airtable and Tray
Tray detects changes in Airtable by running scheduled checks against your bases or responding to events from connected systems, such as a form submission, a CRM stage change, or an engineering event. These signals trigger workflows that create or update Airtable records, apply field mapping logic, and keep your bases synchronized with the rest of your stack.
Once triggered, workflows apply branching logic against record field values and status, call connected systems to enrich or act on the data, and write results back, updating records in Salesforce or HubSpot, creating issues in Jira, notifying teams in Slack or Microsoft Teams, or syncing records to Google Sheets or Snowflake for reporting. They can also be exposed as agent tools.
Integrations
Integrations with Airtable and Tray
Airtable sits at the center of how many teams manage operational data, with bases and tables shaped to fit specific workflows rather than forced into a rigid system. Tray connects those bases to the tools your teams already use: CRMs, marketing platforms, engineering tools, data warehouses, and any system that needs to read from or write to your Airtable records. The connections you define here also power the automations and agents your teams use.
Airtable integration capabilities
Integrate Airtable with 700+ applications plus any system with an API using our HTTP connector. These domains reflect how teams work in Airtable.
Write data into Airtable from anywhere in your stack
- Create records from external events: Add new records to any table when events fire in connected systems, like CRM updates, form submissions, product events, or billing changes
- Update records from downstream outcomes: Write approval decisions, status changes, and field updates back into Airtable records when workflows complete in connected tools
- Batch create records at scale: Use create operations to ingest multiple records at once when syncing data from external sources or migrating between systems
Agents
Build agents with Airtable and Tray
Tray agents turn Airtable records into action. They ground on approved base and table context by reading records, checking field values, and querying across tables, then call governed tools across your stack to update systems, trigger processes, and write outcomes back to the right records. Every result stays traceable, so teams can act on Airtable data and audit what happened.
Ground agents with the record context they need to act accurately
- Object scope: Access records across approved bases and tables, scoped by the bases granted during authentication
- Freshness: Query records at run time using list and get operations; filter by field value, status, or date range to retrieve current state
Frequently Asked Questions
Find answers to common questions about our products and services.
What does Tray add beyond Airtable's built-in automations?
Airtable's native automations run within a single base and are capped at 50 per base with 25 actions each. Tray connects Airtable to external systems with no such limits, enabling workflows that read from and write to multiple bases, CRMs, engineering tools, data warehouses, and any connected system.
Can Tray sync records between different Airtable bases?
Yes. Tray can read records from one base and create or update records in another, enabling cross-base sync workflows that Airtable's native automations can't support without scripting.
How does Tray connect to a specific base and table?
Tray operations target a specific base ID and table name or ID. During authentication, you grant Tray access to the bases or workspaces you want to connect, scoping its access to only the data you choose to expose.
Can Tray handle large Airtable tables with many records?
Yes. Tray workflows handle pagination automatically when listing records from large tables, ensuring all records are retrieved reliably without hitting Airtable's API rate limits.
How do approvals work for sensitive record operations?
Workflows can require human sign-off before creating, updating, or deleting records in production bases, routed through Slack, email, or any connected channel.
How do teams typically start with Airtable + Tray?
Most teams begin with a single workflow, such as syncing a new Airtable record to their CRM or creating an issue in their engineering tool when a record reaches a ready state, then expand to more bases and destinations from there.
FAQs
Yes. Tray can read records from one base and create or update records in another, enabling cross-base sync workflows that Airtable's native automations can't support without scripting.
What comes standard with Tray
Whether your systems, data, or models run in the cloud or on-premises, Tray connects them in one secure platform. Every connection, workflow, and agent operates under IT governance with encryption, audit logging, and access controls built in. Security teams can trust that all integrations comply with enterprise network and authentication policies.
Universal connectivity
- Prebuilt connectors: 700+ connectors plus a universal HTTP connector for any REST API
- Custom connectors: Build custom connectors that behave like native ones
- Connect anywhere: Cloud or on-prem systems supported
On-premises connectivity
- Connect securely: Access on-premises systems, whether first-party or third-party
- Meet network requirements: Connect through approved configurations that align with enterprise security policies
- Enterprise protocols: Support multiple on-premises security standards for safe integration
Authentication management
- Secure credentials: Collect and store authentications with full encryption
- Encrypted data: Protect all data at rest and in transit
- Role-based control: Partition credentials by workspace and access level
Security and governance
- Certified compliance: SOC 2 Type II, GDPR, CCPA, HIPAA
- End-to-end protection: Encryption, detailed audit logs, scoped connections, and OAuth scopes