Showing ideas with label APIs.
Show all ideas
Submitted on
Oct 27, 2021
05:45 PM
Submitted by
TroyTessalone
on
Oct 27, 2021
05:45 PM

Airtable Standard API Add endpoint to duplicate a Record, same as can be done via the UI.
Settings
Record ID
Fields to include (ALL, NONE, Specify Subset)
Example This can be used to clone a template Record.
... View more
Submitted on
Feb 28, 2022
02:01 AM
Submitted by
Augustin_Clouti
on
Feb 28, 2022
02:01 AM

We need a new event type in airtable for deleted records, so that we can trigger actions either in automations or in Zapier / MAKE based on that event. Example: When a record is deleted in airtable, I need to delete corresponding data in another database (external tool)
... View more
Submitted on
Nov 20, 2020
10:18 AM
Submitted by
Amit_Merckado
on
Nov 20, 2020
10:18 AM

I would love to have an automated way to create a new view. Would need to have view attributes, hidden fields, filters, sort, grouping, visibility, etc
... View more
Submitted on
Mar 06, 2020
01:52 PM
Submitted by
Joseph_Sondow
on
Mar 06, 2020
01:52 PM

Some APIs such as AWS allow you to have two working API keys at the same time so that you can rotate in the new one and rotate out the old one without requiring any downtime of your application. I suggest adding a similar feature to Airtable’s API key regeneration procedure so we can rotate API keys without requiring application downtime. Four different functions: Create New API key (maximum of two or three keys perhaps) Enable a disabled key Disable an enabled key Delete key
... View more
Submitted on
Jul 13, 2020
01:25 PM
Submitted by
Mike_Pennisi
on
Jul 13, 2020
01:25 PM

The Scripting Block offers a number of asynchronous functions for collecting input from the user. To date, all the example scripts I’ve seen use these APIs one at a time in a sequential fashion, e.g. const name = await input.textAsync('What is your name?');
const birthplace = await input.textAsync('Where were you born?'); This pattern is serviceable, but it produces an unideal user experience: users are led on a forced march through one question at a time. That can be disorienting when folks run a script for the first time, and that’s particularly apparent when more input is required. Given that the APIs all return Promises, I expected to be able to compose them in parallel and prompt the user for all input simultaneously, e.g. const [name, birthplace] = await Promise.all([
input.textAsync('What is your name?'),
input.textAsync('Where were you born?')
]); That would show users the full extent of the required input “up-front” and offer them the freedom to provide it in a sequence of their choosing. In the Scripting Block today, the second code example does not function as intended. the UI is initially rendered according to the use case (both input fields are present) entering data into either field causes a “spinner” animation to be appended to the document (somewhat confusing, but not entirely disruptive) entering data into the second field causes an error to be displayed, e.g. ERROR
R: userInputStartTime
at main on line 30
... View more
Status:
New Ideas
Submitted on
May 11, 2023
11:22 AM
Submitted by
dk82734
on
May 11, 2023
11:22 AM

How can Airtable Enterprise Audit Logs be sufficient when they exclude record-level revision histories? This seems like a MASSIVE oversight. Am I missing something else here? Original article: https://community.airtable.com/t5/development-apis/reading-revision-history-via-script/td-p/37318
... View more
Submitted on
Apr 06, 2022
10:37 AM
Submitted by
TroyTessalone
on
Apr 06, 2022
10:37 AM

Ability to search for the Automation run history for matching data points in order to narrow down the result set, which can be helpful when troubleshooting errors.
... View more
Status:
New Ideas
Submitted on
Jul 03, 2023
03:48 PM
Submitted by
Daniela_Hecht
on
Jul 03, 2023
03:48 PM

Easy integration and sync with hundreds of apps for non Json-speakers
... View more
Status:
New Ideas
Submitted on
Mar 08, 2023
10:40 AM
Submitted by
Chris_Luc
on
Mar 08, 2023
10:40 AM

What is the proposed idea/solution? A toggle to exclude any changes made via API in a record's Revision History. How does is solve the user problems? We have daily (some hourly) API updates to our records, which makes the Revision History too noisy to read when we're looking for changes made by actual users. Who is the target audience? Any users with regular API/Zapier/Make/etc automations linked to their bases.
... View more
Submitted on
Sep 20, 2021
09:07 AM
Submitted by
vero
on
Sep 20, 2021
09:07 AM

In order to keep our tables under the imposed limit, we want the person who created the table to effectively act as its owner, monitoring its record count and taking action on this as needed.
... View more