Not getting latest info on Airtable

General
1

I have created an action on pickaxe to connect to a Airtable MCP server

I can query the airtable table on existing data

However whenever I add a new record to Airtable, Pickaxe is unable to get the latest info

I have even disconnect and reconnect to the action so that I can get the latest data but it doesn’t work

This seems to be recurring problem whenever I add new data. I did an make,com workflow on Google Sheet and it’s also have the same issue

Does anyone manage to get Airtable working pickaxe action ?

Thanks

1 Like
2

Hello @netmstr

Short answer: If you’re only talking to Airtable, skip MCP. Use a webhook.
Pickaxe “Make webhook” >> Make.com “Custom Webhook” >> Airtable “Search Records”.

Make.com setup (Airtable >> Search Records)

  1. Trigger: Webhooks → Custom webhook. Copy the URL.
  2. Airtable step: Search Records. Configure as follows:
  • Connection: your Airtable PAT connection.
  • Base: choose your base (or toggle Map to take it from the webhook payload).
  • Table: choose your table (or Map it).
  • Sort: toggle ON >> Add item
    • Field: your reliable timestamp (e.g., Created time or Last modified time).
    • Direction: Descending.
      3.(This guarantees newest is first.)*
  • View: leave empty while testing (views can hide new rows).
  • Output Fields: leave empty to return all, or pick exactly what you need.
  • Formula (optional): add filters only if you need them (e.g., a time window).
  • Limit: set to 1 if you only need the latest record. Increase if you need more.
  1. Save and Run once to lock the schema.

image
image502×1067 57.9 KB

(Note: This is only an example configuration schema for demo purposes)

Pickaxe

  • Add a Make webhook step and point it at your Make Custom webhook URL.
  • Send whatever inputs you want to Map in Make (e.g., base, table, sort field, limit).

Notes

  • If you use a View, make sure it actually includes newly added rows; otherwise leave it blank.
  • The Limit field in Make’s Airtable module controls how many rows you get back; for “latest only,” keep it at 1.
  • If you don’t have a Created time column, add one (or use Last modified time).

If they want more than one API later (Airtable + something else), then it starts to make sense to use an MCP server.

1 Like
3

Wow what a detailed answer, thanks a lot

Since this is an API call. So theoretically I would like need to create 3 make.com API call

  1. for searching
  2. for insert
  3. for deletion

Correct ?

1 Like
4

@netmstr You’re welcome! Great question.

Short answer: you don’t need three “Make an API Call” modules. Use Make’s native Airtable modules instead:

Search >> Airtable → Search Records
Insert >> Airtable → Create a Record (or Upsert a Record if it might already exist)
Deletion >> Airtable → Delete a Record

Tip for “latest row”: in Search Records, set Sort to your timestamp field descending and set Limit to 1.

5

But this is 3 api call right?

How do you update, delete or insert new record with only 1 api call?

1 Like
6

@netmstr Great question. Think of it this way:

  • Airtable’s API is one operation per request. There isn’t a single endpoint that can search + insert + delete in one shot.
  • You can still keep one automation flow and run exactly one Airtable action per run (search or create/update or delete).

Use Make’s native Airtable modules (simpler than “Make an API Call”):

Search >> Airtable >> Search Records
Create or Update >> Airtable >> Upsert a Record (one module handles create-or-update)
Delete >> Airtable >> Delete a Record (one call if you already know the recordId; if you don’t, do Search >> Delete)

For “latest row,” set Sort to your timestamp field descending and Limit to 1 in Search Records.

Need to affect many records at once? Use the Bulk Create / Bulk Update / Bulk Upsert / Bulk Delete modules. There is still one call per operation type, but they handle multiple records efficiently