How to Setup Airtable CRM with Microsoft Dynamics 365 (2026 Guide)

Why Use Microsoft Dynamics 365 with Airtable

Microsoft Dynamics 365 is a comprehensive enterprise CRM that handles complex sales processes, customer service, and business operations. Airtable is a flexible, spreadsheet-like database that many teams use as a lightweight CRM for its ease of customization and visual interfaces. Using both together gives you the power of Dynamics 365 for official customer records with the agility of Airtable for ad hoc tracking, project management, and custom workflows.

Teams often turn to Airtable when Dynamics 365 feels too rigid for certain use cases. A partnerships team might track co-marketing activities in Airtable because they need custom views and Kanban boards that are faster to set up than Dynamics 365 custom entities. A product team might use Airtable to track customer feedback linked to CRM contacts. Rather than building everything inside Dynamics 365, Airtable provides a flexible layer on top.

Another common use case is creating simplified front-ends for Dynamics 365 data. Airtable's interface designer can present a clean, focused view of customer data that non-CRM users (executives, support staff, operations) can interact with — without needing a Dynamics 365 license or training on its complex interface.

What You Can Do

• Mirror key Dynamics 365 contact and account data in Airtable for easy access
• Use Airtable as a flexible front-end for specific Dynamics 365 datasets
• Track supplementary data in Airtable (events, partnerships, feedback) linked to Dynamics 365 records
• Build custom dashboards and Kanban views in Airtable using Dynamics 365 data
• Push updates from Airtable back to Dynamics 365 to keep the source of truth current
• Sync data via Power Automate, Zapier, Make, or the Airtable API
• Create intake forms in Airtable that feed into Dynamics 365 workflows

Prerequisites

• A Microsoft Dynamics 365 account with API access enabled
• An Airtable account (Pro plan or higher recommended for API access and automations)
• Admin access to both platforms
• An integration platform: Power Automate, Zapier, or Make
• Your Airtable API key or personal access token (found in Account settings)
• Azure AD app registration for Dynamics 365 API access
• A clear plan for which data lives in each system and the sync direction

Step-by-Step Setup Guide

Step 1: Define Your Use Case and Data Architecture

Decide how Airtable will supplement Dynamics 365. Common patterns include: (A) Airtable as a read-only mirror of select Dynamics 365 data for non-CRM users, (B) Airtable as a workspace for supplementary data that links back to Dynamics 365 records, or (C) Airtable as an intake layer where new data is collected and then pushed to Dynamics 365. For each pattern, identify which fields need to sync and in which direction. Establish Dynamics 365 as the system of record for core customer data — contacts, accounts, and revenue data should always be authoritative in Dynamics 365.

Step 2: Design Your Airtable Base

Create an Airtable base with tables that correspond to the Dynamics 365 data you want to work with. For a contact mirror, create a table with fields for Name, Email, Company, Phone, Deal Stage, and a Dynamics 365 Record ID field (single line text) to store the unique identifier from Dynamics 365. This ID field is critical — it allows the integration to match Airtable rows to Dynamics 365 records. Add any supplementary fields that are Airtable-only (e.g., Event Attendance, Partner Notes, Feedback Category). Use Airtable's field types strategically — single select for status fields, linked records to connect contacts to companies, and attachment fields for documents.

Step 3: Set Up the Integration Connection

Power Automate is a strong choice here since it connects natively to Dynamics 365. Create a new flow in Power Automate. For the Dynamics 365 side, use the Dataverse connector (the modern connector for Dynamics 365). For Airtable, use the Airtable connector available in Power Automate, or use HTTP actions to call the Airtable API directly. If using Zapier, both Dynamics 365 and Airtable have well-supported native connectors. Authenticate both services and test the connections.

Step 4: Build the Dynamics 365 to Airtable Sync

Create a flow triggered by new or updated records in Dynamics 365. For each triggered record, search Airtable for a row with a matching Dynamics 365 Record ID. If found, update the existing Airtable row. If not found, create a new row and populate the Dynamics 365 Record ID field. Map all relevant fields from the Dynamics 365 record to Airtable columns. For the initial data load, you may need to run a bulk sync. Export a filtered view from Dynamics 365 as CSV, then import it into Airtable and populate the Record ID field to establish the link.

Step 5: Build the Airtable to Dynamics 365 Sync (If Needed)

If your use case requires pushing data from Airtable back to Dynamics 365, create a reverse workflow. Use Airtable's automation triggers (when a record is updated or when a record enters a specific view) to initiate the sync. Use the Dynamics 365 Record ID stored in Airtable to find and update the correct Dynamics 365 record. Be selective about which fields sync back — typically only fields managed in Airtable should write back to Dynamics 365, while fields managed in Dynamics 365 should only flow to Airtable.

Step 6: Build Airtable Views and Interfaces

With data flowing into Airtable, build the views that make this integration valuable. Create a Kanban view grouped by deal stage for visual pipeline management. Create a Gallery view for account profiles. Use Airtable's Interface Designer to build dashboards with charts showing pipeline value, activity counts, and other metrics. Share these interfaces with team members who do not have Dynamics 365 access. Set up filtered views for specific teams or regions so everyone sees only the data relevant to them.

Practical Examples

Executive Dashboard

Key opportunity data from Dynamics 365 syncs to Airtable nightly. The leadership team uses an Airtable interface with charts showing pipeline by stage, top deals by value, and win/loss ratios. Executives get the visibility they need without Dynamics 365 licenses or training.

Event and Partnership Tracking

The partnerships team tracks co-marketing activities, event sponsorships, and partner contacts in Airtable. Each partner record links to the corresponding Dynamics 365 account via the Record ID field. When a partnership closes a deal, the team updates the Dynamics 365 opportunity via the integration, keeping revenue data accurate in the enterprise CRM.

Customer Feedback Collection

An Airtable form collects customer feedback from the support team. Each submission includes the customer email, which triggers a lookup in Dynamics 365 to enrich the Airtable record with account details. Product managers review feedback in Airtable's grouped views, while a summary score syncs back to the Dynamics 365 contact record for sales reps to reference.

Simplified Sales Intake

New inbound leads are entered into an Airtable form by the receptionist or a chatbot integration. A Power Automate flow picks up new Airtable records and creates leads in Dynamics 365 with full field mapping. The sales team works entirely in Dynamics 365, while the intake process stays simple and accessible in Airtable.

Tips and Troubleshooting

• Always store the Dynamics 365 Record ID in Airtable: This is the key to reliable syncing. Without it, you will rely on email or name matching, which is fragile and can cause duplicates.
• Airtable API rate limits: Airtable allows 5 requests per second per base. For large initial syncs, batch your operations and add rate limiting to your Power Automate or Zapier workflows.
• Keep Airtable supplementary, not duplicative: Avoid recreating all of Dynamics 365 in Airtable. Sync only the fields that are needed for your specific use case. This reduces sync complexity and avoids data conflicts.
• Use Airtable Automations for lightweight triggers: Airtable's built-in automations can send notifications, update fields, and trigger webhooks without needing an external integration platform for simple tasks.
• Handle deleted records: Decide what happens when a record is deleted in one system. Most integration platforms do not sync deletions by default. Consider adding a "Status" field with an "Archived" option rather than deleting records.
• Watch for Airtable record limits: Airtable bases have row limits depending on your plan (50,000 for Pro, 250,000 for Enterprise). If your Dynamics 365 database is large, sync only a filtered subset to Airtable.