I’m trying to set up a system that detects when a new Airtable base is created. I’ve looked into webhooks, but they need a base ID, which doesn’t work for my use case. I’ve also tried polling the List Bases API, but it doesn’t give me any time-related info.
Does anyone know a way to get the creation or last updated time for Airtable bases? I’ve gone through the API docs and couldn’t find anything helpful. Is there a workaround or hidden feature I’m missing?
I’m open to any suggestions or alternative approaches. Maybe there’s a way to compare base lists over time? Or perhaps there’s an undocumented API endpoint that could help? Any insights would be greatly appreciated!
have u tried using the metadata endpoint? it might not give exact timestamps, but u could track changes by comparing metadata snapshots over time. another idea: set up a custom webhook receiver and use airtable’s automation to ping it whenever a base is modified. not perfect, but could work as a workaround
I’ve faced similar challenges with Airtable’s API limitations. One workaround I’ve found effective is implementing a periodic snapshot system. Essentially, you’d create a script that runs at regular intervals (say, every hour) to fetch the complete list of bases. By comparing this list against the previous snapshot, you can identify new bases and infer their creation time within the snapshot interval.
For tracking modifications, I’ve had success with a hybrid approach. Combine the snapshot method with targeted API calls to individual bases, checking for changes in table structures or record counts. This gives a reasonable approximation of when bases were last modified.
While not perfect, these methods have proven quite reliable in my projects, offering a good balance between accuracy and API usage efficiency. Just remember to respect Airtable’s rate limits when implementing such solutions.
Airtable’s API indeed has its limitations as it doesn’t directly supply creation or modification timestamps for bases. From personal experience, one feasible approach is to design a custom logging system where you capture base IDs the moment you encounter them. This might involve storing base identifiers together with a timestamp in a separate database. While this method may not be foolproof in catching fast-moving changes, it provides a detectable trail of base creation events. Additionally, exploring the Automations feature could offer an alternative, though it typically requires creative configuration to suit these needs.