This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Video support is really limited at the moment:Attachment fields support videos, but it’s not super useful for managing video content as you have to actually click into the content to see what it is.It would be a huge help if the table views supported...
Fetch request is built like this, including these headers:
But it returns a CORS error — the webhook isn’t returning Access Control Allow Headers…
Oddly enough I can get it to work from Postman:
And if I follow the proxy outlined here it works as ...
The Web Clipper is an amazing feature, I’m using it frequently to clip LinkedIn profiles into a CRM. Unfortunately I still need to open the new records in Airtable so I can add their company — would be great to create a new record from within the cli...
TLDR; it’d be dope to have a new method in the Airtable API that allows you to trigger a base’s sync.
I have two bases: one for a crm, and one for projects.
The projects base has a table for projects, and two synced tables from the crm, one for peopl...
Title says the root of the problem. I’m thinking this is because CORS, but I’ve had no luck with fetch or the newly introduced remoteFetchAsync.
Finding the same thing with two different APIs:
Creating a customer in Stripe (this one works in automati...
Any updates on this? How's everyone handling cross-origin requests in their Airtable scripts? Just writing serverless functions elsewhere and calling those?
Posted this before I saw the video snippets app. This definitely helps, but doing this by default in the gallery view / enabling it as an option in other views would be really useful.
Thanks for the details.
Erin from the community team reached out to confirm that the incoming webhook trigger doesn’t currently support CORS. The reason it works on Zapier / Postman is because they execute the requests from their servers, rather than...
For more context, I tested it out with Zapier Webhook and it passed when I removed all the headers from the fetch options:
const fetchOptions = {
method: 'POST',
body: formDataJsonString,
};
but this same header-less payload still returns a ...
