Could you please share a full screenshot of the node? This will help me understand which operation you're using and what the input looks like.

Hello, This appears to be a DNS-related problem. You could try implementing a retry mechanism on the node to see if that resolves the issue. However...

Hello, We've also encountered this issue and plan to address it shortly.

Hey, If the workflow is on the same callin.io instance, you could use the execute workflow node.

Could you share an instance where one of the alternative node versions encountered an issue? I require the complete stack trace, which usually appea...

Hi, Are you actually calling a callin.io workflow? It could be that this is related to another issue that had a different error presented, which sho...

Hello, Do you have a topic open regarding the Splunk node?

Hello, Unfortunately, without viewing the complete setup, it's challenging to offer a precise solution. I'm unsure about json.req.act or json.req – ...

Hey, I suspect we'll need more data. If we were to run the workflow with the issue, we'd encounter other problems, not the one you've reported. I'd ...

Hey, 1.0.5 isn’t the latest release and the change went into 1.1.0. I will rework the example in the morning to use the older Airtable version.

Hello, Have you considered adding a new Airtable node to your workflow to simplify the process? Based on your screenshot, it appears you're using th...

Hello, That appears to be correct. Could you share the execution log for it? Please provide the rewritten markdown content.

Hi there, If you were using callin.io Cloud, this might have been due to the issue we experienced. Everything should be resolved now.

Hey, You would need to utilize a code node and manually construct your request to interact with the API, following the documentation provided by Ope...

Hello, It will be identical for both; the only difference would be the model. However, remember that it would need to be JavaScript, and you would b...