After 10 hours I finally narrowed down the source of why my Airtable API POST Call was not working. Since the actual make.com tools made to post to Airtable are unusable basically.
I need further assistance however, I cannot get it to work, I have narrowed it down to an array that maybe I am not mapping properly…
1: I am Splitting Text, a social media post that starts off with the title, " THis is Post Title || This is Post Content", I am splitting that using Set Variable Module:
- Next, Here is the array output:
- Next, I attempt to map the Array output (Not sure what it’s really called) to the fields “Post Title” and “Post” in the API Call. When I first set it up the closing bracket (Not sure what it’s called is Purple) but after I run the scenario, even though the proper Post Title and Post Content TEXT IS INSIDE OF THE “Request Content” where it should be, the API Call breaks with error:
*****Error: 422 Unprocessable Entity
- {“error”:{“type”:“INVALID_REQUEST_BODY”,“message”:“Could not parse request body”}}*****
AND, THE PURPLE CLOSING BRACKETS for the ARRAY (pieces) ARE NOW OUTLINED NOT FILLED IN PURPLE.
Here is the complete body of the API Call:
{
“records”: [
{
“fields”: {
“Post Topic”: “Luxury Custom Homes and Interiors”,
“Post Subtopic”: “Exclusive Design Consultation”,
“Post Title”: “Designing Your Dream: The Power of Personalized Design Consultation in Southeast Michigan”,
“Post”: "In the ever-evolving world of luxury custom homes, staying ahead of industry trends is paramount. Southeast Michigan is seeing a surge in personalized home design, blending cutting-edge technology with timeless aesthetics. This is where our exclusive design consultation steps in, offering bespoke solutions for those dreaming of a luxury haven tailored perfectly to their lifestyle and taste.
At Haus Custom Homes, our consultation process begins with understanding your unique preferences and needs. From selecting the ideal site to choosing materials that reflect your identity, every aspect of your luxury home planning is curated with precision. As trends lean towards sustainability and smart home technologies, our design experts ensure these elements are seamlessly integrated, enhancing both comfort and functionality.
Whether you’re looking to incorporate minimalist elegance or opulent warmth, our personalized consultation will transform your vision into a luxurious reality, making your home not just a residence, but a reflection of your highest aspirations.",
“Location”: “Southeast Michigan”,
“Post Link URL”: “https://www.hauscustomhomes.com”,
“Image Prompt”: “Realistic Photograph, Cinematic composition, Close up, Architectural consultation session, modern luxurious office, couple attentively listening to architect, detailed blueprints and 3D models, sleek minimalist decor, large windows, view of Southeast Michigan’s green landscape --ar 16:9 --v 6”,
“Image”: [
{
“url”: “https://cdn.renderform.io/AyP47SXDoOHIsP9Oomxi/results/req-284cae0d-fc68-4afc-a59c-1136e47c0a54.jpg”
}
]
}
}
]
}
- If I remove the mapped array parts from within the API Call body, the Request works fine… I feel like the white unfilled in bracket at the end is an indicator of why this isn’t working??
UPDATES
UPDATE 1:
I left the first part of the mapped array but removed the second part to try and isolate the issue, and now the API Call functions properly, below is the part that I removed, which is LONG TEXT and goes into a LONG TEXT FIELD inside of Airtable, so I think I need to set up the API Call differently for LONG TEXT(?)…
UPDATE 2:
I manually inserted LONG FORM TEXT into the API Call into the “Post:” (Field? Variable?) which may further confirm the need to handle the LONG TEXT going into a LONG TEXT FIELD in Airtable inside of the API Call.
UPDATE 3:
Now I copied and pasted the NON WORKING Request Content Body code or whatever its called, and THE API CALL WORKS, even with long text, so as usual, none of this makes any sense…
(NO LONGER) REOLVED-ISH:
This isn’t a solution. But what I did was I copied the API Call “Code” that WASNT WORKING Above, you can also see the error above, then pasted it into the HTTP “Request a Call” Module, then just replaced the text with the mapped variables from the scenario and it worked.
If this didnt work I was going to just ELIMINATE THE TEXT SPLIT, and generate the Post Title and Post Content speerately then map them to the API without the Array.
It would take 3 weeks for an expert to figure out why this isn’t working properly and that will never happen so…
BUt here is the complete body of the working API CALL:
{
“records”: [
{
“fields”: {
“Post Topic”: “{{89.Topic Randomizer}}Custom Homes Design and Build”,
“Post Subtopic”: “{{113.Subtopic}}”,
“Post Title”: “{{115.Split Post Title[1]}}”,
“Post”: “{{115.Split Post Title[2]}}”,
“Location”: “{{145.Location Randomizer}}”,
“Post Link URL”: “{{113.Link URL}}”,
“Image Prompt”: “{{139.result}}”,
“Image”: [
{
“url”: “{{130.href}}”
}
]
}
}
]
}
