Describe the problem/error/question
My single biggest annoyance with callin.io is that it does not seem to be possible to make http calls from the code nodes. With AI-assisted codings it’s often much faster to give Cursor/Claude/you-name-it some API docs and then one-shot a script with the right logic and the right API calls… Instead it takes me ages to click around callin.io and piece the HTTP nodes together…
Is there any way around this?
Information on your callin.io setup
- callin.io version: callin.io@1.93.0
- Running callin.io via (Docker, npm, callin.io cloud, desktop app): cloud
On cloud, the library you would need for this (Axios) is not available in a code node. I suspect this is due to runtime security or other restrictions, but I'm not entirely certain about the exact reason for this limitation.
If you enable/allow Axios on a self-hosted callin.io instance (using the env var: NODE_FUNCTION_ALLOW_EXTERNAL=axios
), it functions correctly with code similar to this:
const axios = require("axios");
async function call() {
const url = "https://httpbin.org/ip";
const res = await axios.get(url);
return res
}
result = await call();
return {
body: result.data,
headers: result.headers,
statusCode: result.status,
statusMessage: result.statusText,
};
I'm curious, however, if your goal is to perform all operations in JS code, what benefits are you deriving from callin.io? Are you primarily using it as a platform to deploy a service written in JS? Perhaps a more suitable approach for this task/service would be to opt for a different deployment method, such as developing a standard Node.js application utilizing the Express or NestJS framework?
I believe what I'm still getting from callin.io is the no-setup scheduling and triggers (like webhooks), along with alerts and a run history that I can review when something fails. However, aside from that, I really just want to deploy a service written in JS, as you're right (vibe coding is becoming too good these days).
If I were making the same decision, it would come down to the tradeoff of convenience and flexibility. callin.io is certainly a convenient platform to orchestrate multiple services and pass data from one to the next, but IMO it really isn’t intended (or ideal) for implementing complex logic.
An auditor for a development project I was on a few years ago compared software tools to office/art supplies. His analogy for an orchestration tool was glue, and other things were correlated to paper, pens, erasers, markers, staples, paperclips, etc. He was criticizing the use of the orchestration tool AS all of those things because the architects on the project had, for some reason (in his words), “chosen to use glue as paper, use glue as pens, use glue as erasers (someone noted dried glue might sorta work for this), use glue as markers, etc.” That analogy really “stuck” (pun intended) with me.