Auto-enrich new Airtable prospects with Datagma

By General Input

When a new prospect lands in Airtable, find their verified work email, mobile, title, and company details, then write everything back to the row.

Integrations

  • Airtable
  • Datagma

Type

Deterministic Code

Categories

  • Sales
  • Operations

Build a code workflow that auto-enriches new prospect rows in Airtable using Datagma so SDRs work from populated records instead of bare LinkedIn URLs.

Trigger: Airtable poll, event type new_record, on my Prospects table. I will configure the base and table at setup.

Step 1. Airtable Get Record. Read the newly created record so we have its current values for linkedin_url, full_name, and company. Use the record id from the trigger payload.

Step 2. Datagma Enrich Person or Company. Call this with the LinkedIn URL when present, otherwise fall back to full_name plus company. Set personFull=true, companyFull=true, and phoneFull=true so we get the verified work email, mobile, current title, seniority, company size, industry, country, and technologies. Treat the response carefully: a 200 OK with code 5 means not found, not a successful match. Code 3 means a bad argument or bad API key and should surface as a workflow error.

Step 3. Airtable Update Record on the same record id. Map Datagma fields into the row: work_email, mobile_phone, current_title, seniority, company_size, industry, country, technologies. Only write a column when Datagma returned a value for it, so existing rep-entered data is not blanked out. Also set enrichment_status to enriched.

Not-found branch. If Datagma returned code 5, skip the field map and call Airtable Update Record with enrichment_status set to not_found. The outbound view filters on enrichment_status = enriched, so not_found rows drop out cleanly instead of looking like a successful enrichment with blank fields.

Error handling. On any non-code-5 failure from Datagma, set enrichment_status to error and include a short reason in an enrichment_notes column so I can retry later. Do not silently swallow the error.

Field mapping is fixed and deterministic, the inputs are structured, and there is no agent reasoning required, so this should be built as a code workflow with discrete nodes.

Related prompts

Explore more prompts
Creator roster board for rebook, test, or pause callsRun your nutrition clients' weekly meal plans from one consoleInstagram UGC rights tracker and repost approval boardA verification desk for every document your team scansBrowse and shortlist creators without burning audit creditsGlobal operations exposure map for your sites and suppliersDeal sourcing kanban board for your Harmonic saved searchesProof client shoots and hand off the delivery album in one placeField service dispatch board that ranks the closest techVendor due diligence register with on-demand risk briefs