Hello, What you're observing is anticipated behavior. You've configured the webhook trigger to respond with the output from the respond to webhook n...

Hey, Welcome to the community Have you considered storing the webhook request data in a database for future workflow runs? Perhaps using a too...

That's an interesting concept, and it has my support.

Good news, this may be resolved shortly with this PR: feat(Loop Over Items (Split in Batches) Node): support multiple runs by elsmr · Pull Request #87...

Hello, Looping within a loop can indeed be challenging. It appears you've made progress by looping back from the order table, but there are a couple...

Hello, Welcome to the community It appears the missing piece is the WEBHOOK_URL environment variable. I suggest removing the changes you made to...

Hello, This would apply to any field where Postgres is assigning the value, rather than you manually entering it. Could you please export the schema...

Hello, Cloud and self-hosted versions will be largely identical, with no functional differences in the callin.io version. The upsert error you're en...

Any ideas what could be going on here?

Hey, It shouldn't be as long as that connection works. Can you try to repull the image to see if that helps?

Hello, The node appears to be functioning correctly on my end. Could you please try executing it independently, without the preceding nodes, to see ...

Hey, Regarding polling, we would check the poll time for any data newer than the timestamp saved from the last execution. If there's no data to co...

Hey, Since our node doesn't offer this functionality, you'll need to make API calls to Airtable using the HTTP Request node, provided Airtable suppo...

Hello, It depends on the volume of data you're writing and your network connection. We don't process Airtable requests in batches, so if you had 100...

Hello, That does appear useful. The newer version of the node utilizes a different component, which we refer to as RMC (resource mapper component). ...