Hello, Looking at the API example, you could utilize an HTTP Request node to send the request. However, it appears the function needs to be executed...

Hi there, We do not currently have a function option within the node. I've just created an internal development ticket to implement this feature. Ho...

Hi there, Could you please share the output from the node that's encountering the error, along with the content it's attempting to post? Based on th...

Hey, You won't want to replace all of them. Have you run your output through a JSON linter to see if it shows as valid? Please provide the rewritt...

Hello, In theory, all characters are permitted. However, if your string begins with a " character, it will anticipate the next " character as the en...

Hey, If this issue only occurs during specific runs, it's likely related to the data. The example you shared appeared invalid, so I suspect similar ...

Hey, That JSON appears to be invalid. You have unescaped " characters within your data, which will lead to problems. Could you share your workflow...

That sounds like a request for Airtable to return that in their API messages

Hey, It should function with the code node too. Based on your output, the issue is likely that 'status' is in lowercase. If it were capitalized as S...

Yes, that should resolve it. In the Set node, check the option at the top, then add 'id' and 'Status' as two options, and you should be all set.

Hey, Welcome to the community Do you have a field in your Airtable named Meeting Scheduled? I suspect if you clear the expression from the Fie...

I don't see anything that should be preventing it from functioning. What data type is configured for the Content field in Airtable?

Hi, The HTTP Request node isn't named HTTP Request1 in your workflow. You'll need to adjust the name or try using {{$json["choices"][0]["text"]}} in...

Hey, Welcome to the community When you mention it's unable to detect the set > content value, what exactly do you mean? Looking at the flow...

Hello, Could you please try Marcus's suggestion and remove the expression from the Fields, typing in sent_status instead, unless your field name is ...