Trouble with Airtable script sending POST requests to custom API

Other Questions Airtable
1

I’m having issues with my Airtable script. It’s supposed to send data to my API using a POST request, but something’s not right. When I run the script, it hits my API with an OPTIONS method instead of POST, resulting in a 405 error.

Here’s what’s weird: the API works fine when I test it with Postman. But in Airtable, I get this error:

TypeError: Failed to fetch
at main on line 27
This error might be related to Cross-Origin Resource Sharing (CORS)

The console shows:

OPTIONS /api/webhook 405 Method Not Allowed

I’ve got a Node.js backend handling the requests. It seems like the OPTIONS request is being triggered, but I can’t figure out why. I’ve tried adding headers to allow POST requests, but no luck so far.

Has anyone run into this before? Any ideas on how to fix it? I’m stumped and could really use some help troubleshooting this CORS issue. Thanks!

2

I’ve encountered similar CORS issues when working with Airtable scripts and custom APIs. One thing that often gets overlooked is the Airtable script’s fetch configuration. Try modifying your fetch call to include the ‘mode’ and ‘credentials’ options:

fetch(apiUrl, {
method: ‘POST’,
mode: ‘cors’,
credentials: ‘include’,
headers: {
‘Content-Type’: ‘application/json’
},
body: JSON.stringify(data),
})

This explicitly tells the browser to use CORS mode and include credentials if needed. Also, double-check your API’s CORS configuration. Sometimes, it’s not just about allowing OPTIONS, but also specifying the exact origins allowed.

If you’re still hitting roadblocks, consider using a CORS proxy as a temporary workaround while you debug. It’s not ideal for production, but can help isolate whether the issue is on the Airtable side or your API side.

3

This issue is likely due to your API not properly handling CORS preflight requests. When making cross-origin requests, browsers send an OPTIONS request first to check if the actual request is allowed.

To resolve this, you need to configure your Node.js backend to respond correctly to OPTIONS requests. Add a middleware that handles CORS:

const cors = require('cors');
app.use(cors());

Also, ensure your API routes are set up to accept OPTIONS requests. You might need to add specific headers to your responses:

res.header('Access-Control-Allow-Methods', 'GET, POST, OPTIONS');
res.header('Access-Control-Allow-Headers', 'Content-Type, Authorization');

Implement these changes and test again. If issues persist, double-check your Airtable script for any configuration errors.

4

sounds lyk a classic CORS headache. ur api prolly needs to handle OPTIONS requests for preflight. try adding this to ur node.js backend:

app.options(‘*’, cors()) // enable preflight
app.use(cors())

that might sort it. lmk if u need more help!