Enfocus Community

Noticed a few threads here lately about HTTP Request issues (variables not expanding in v20+, connection errors with third-party systems, and general request failures). Ran into some of the same pain points myself while testing domain lookup calls, so I wanted to share what helped and get input from...

Thanks Freddy, that's helpful. Makes sense to start with the HTTP request element for a single fixed-token call and only move to a script if the auth or logic gets more layered. I ended up testing this with the WhoisFreaks endpoint I mentioned, using just the HTTP request element with a bearer token...

Looking for advice on a workflow pattern: before a job continues through Switch, I want to verify some domain-related information tied to the job, things like checking if a client's domain is still active, confirming registration/expiry dates, or flagging jobs tied to newly registered domains for ex...

Thanks for sharing that, @foxpalace that's helpful. Quick follow-up: are you doing anything for error handling around that axios call, like if the endpoint times out or returns a non-200? Wondering if you're catching it and letting the flow continue with a fallback value, or if you have the script k...

Has anyone here set up a Node.js script in Switch that calls an external REST API to pull in metadata before a job continues down the flow? Thinking of use cases like the following: - Looking up the geolocation of a client's uploaded IP/file source for routing or logging purposes - Checking domain/W...