What can I automate with the httpbin integration?

A dependable place to point a step at while you build a workflow, from httpbin. Send a request and get the whole thing back, so you can see exactly what your workflow sends: the method, the query values, every header and the body. Then force the cases that are hard to arrange for real, and build the branches that handle them: a 500, a 404, a rate limit, a response that takes ten seconds, a chain of redirects, a password or token that gets rejected. It will also tell you which IP address your workflows call from, for a service that keeps an approved list, and hand you a unique ID or a sample document to work against. Nothing is stored and nothing is charged. No account or API key required. Lodol supports 10 actions for httpbin, which you can combine with any other app in a workflow.

How do I connect httpbin to Lodol?

Connect httpbin once in your workspace and every action and trigger it supports can be added to a workflow, by you in the editor or by your AI.

All integrationsUtilities

httpbin

A dependable place to point a step at while you build a workflow, from httpbin.

Start Free Browse all integrations

actions: 10

Actions

Steps a workflow can run in httpbin.

Send a test requestSend a request and get the whole thing back: the method, the address, the query values, every header and the body. The step to put in front of a new integration to see exactly what your workflow is sending before you point it at something real. Nothing is stored and nothing is charged. No API key required.
Simulate a response statusMake httpbin answer with the status you choose, so you can build and test the branch that handles it. The step itself always succeeds, even when you ask for a 500: the status comes back as a value to branch on, because a step that failed would leave nowhere to put the branch. No API key required.
Simulate a slow responseMake httpbin take its time before answering, so you can see how a workflow behaves against a slow service and whether a timeout is set where you think it is. Up to ten seconds. No API key required.
Test following redirectsSend a request through a chain of redirects and see where it ends up. Answers whether Lodol follows redirects at all, and how many deep, which is the usual reason a request that works in a browser does not work in a workflow. No API key required.
Test a username and passwordSend a username and password the way a service expecting them would receive them, and see whether they arrive intact. This is what catches a password with an awkward character in it, or a value that was never filled in from an earlier step. Choose to have them rejected instead and you get the same refusal a real service gives, to build the other branch against. No API key required.
Test a bearer tokenSend a token the way an API expecting one would receive it, and get it read back to you. That read-back is the point: it proves the value your workflow built is the value that left the building. Choose to have it rejected instead and you get the same refusal a real API gives, to build the other branch against. No API key required.
Check the headers we sendSee every header a request from Lodol carries, without setting anything up. Useful when a service is refusing your requests and you need to know what it is actually being handed. To check a header of your own, use Send a test request instead. No API key required.
Check the IP address we call fromFind out which public IP address your workflows reach the internet from. This is the address to give a service that will only accept requests from an approved list. No API key required.
Generate a unique IDGet a fresh unique ID, different every time. For tagging a run, naming a file, or filling a field that has to be unlike every other one. No API key required.
Get a sample documentGet a small nested JSON document, the same one every time. Something real-shaped to build the rest of a workflow against while the payload it will really receive does not exist yet. No API key required.