HttpStatus
Developer ToolsCheck HTTP status codes, redirect chains, and response headers for any URL with the HttpStatus API. Agents verify a link resolves before it goes out in a campaign or a published page.
What This Integration Enables
HttpStatus has three actions. That is not a gap, it is the argument. A link either resolves where you think it resolves or it does not, and this connector answers that question definitively without asking you to adopt a monitoring product to do it. Check URL Status returns the status code and message plus every hop in the redirect chain with its own latency, IP address and same origin or cross origin type, and can optionally return response headers, request headers, the raw request, the destination page body, page metadata including title, description, canonical and hreflang, parsed URL and hostname components, and connection timings. Requests can be sent as a named search engine crawler or browser user agent, over IPv4 or IPv6, with or without TLS certificate validation.
That combination makes it the right tool at a specific moment: the last check before something ships. Before a campaign sends, before a migration's redirect map goes live, before a published page's outbound links are indexed. Get Redirect Chain flattens the same trace into a summary when only the path matters, and Check URLs In Bulk walks a list of up to 100 URLs per run, capturing a failure on one URL in that URL's own result so the remaining checks continue. Requests are always sent as HTTP/1.1 GET with a fixed 10 second server side timeout, which is worth knowing when a slow destination is the thing you are diagnosing. FlowRunner agents run the check, group the results, and put the ambiguous cases in front of the person who owns the link.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Pre send link verification for a campaign
Before a campaign in Mailchimp goes out, a flow collects every destination URL from the draft and runs Check URLs In Bulk. Anything that does not return a final 200, and anything whose chain crosses to a different origin, goes into a summary posted to the campaign channel in Slack. The campaign owner clears or fixes each flagged link, and the send proceeds. The links that were already fine consumed nobody's attention.
Verifying a redirect map after a site migration
A site moves and hundreds of old URLs are supposed to land on new ones. The flow reads the intended mapping from a sheet in Google Sheets, runs Get Redirect Chain against each old URL, and compares the reported final destination against the intended destination, along with the hop count and total latency. Mismatches, redirect loops and chains longer than expected are written back into the sheet with their actual destinations. The migration owner works a list of real discrepancies instead of spot checking.
Ongoing outbound link health on published content
A scheduled flow walks the outbound links on published pages in WordPress in batches, running Check URLs In Bulk on 100 URLs per run. Links returning 404 or 410 are grouped by owning page and opened as editorial tasks. Because the connector reports the redirect chain rather than only the endpoint, links that still technically work but now bounce through a parked domain get flagged in the same pass, which is the case a simple uptime check would call healthy.
Human-in-Loop Highlight
The failure this connector is uniquely able to surface, and uniquely unable to judge, is the link that passes. A URL returns 200 after two hops. The status code is green. What the status code cannot tell you is that the second hop was a cross origin redirect: the link left your domain and now resolves somewhere you did not choose, possibly a parked page, a rebranded acquirer, or an expired partner domain picked up by someone else. HttpStatus reports the origin type on every hop and can return the destination page's title and canonical, so the agent can see that the chain left the original host and what the endpoint now calls itself. It cannot decide whether that destination is still the right place to send a customer.
So the agent splits the batch. Clean single origin resolutions pass silently. Everything that crossed origin stops: "Three links in the July nurture sequence now redirect off site. 'partner-offer.example' resolves in two hops to a page titled 'This domain may be for sale'. Ship, replace, or remove?" The campaign owner answers. This is the human-in-the-loop pattern that matters for a read only connector: the agent gates the decision that follows the check, not the check itself, because sending customers to a domain that changed hands is the sort of mistake that is cheap to prevent and expensive to explain.
Agent Capabilities
3 actionsURL Checks
2- Check URL Status Checks a single URL and returns its HTTP status code, status message, and the full redirect chain with per hop latency, IP address, and same origin or cross origin redirect type. Optionally returns response headers, request headers, the raw request, the destination page body, page metadata, parsed URL and hostname components, and detailed connection timings. Requests are always sent as HTTP/1.1 GET with a fixed 10 second server side timeout.
- Check URLs In Bulk Checks a list of URLs and returns one condensed result per URL with its final status code, destination URL and redirect count, plus counts of how many checks succeeded and failed. The API accepts a single URL per call, so this operation issues the calls sequentially with a short pause between them to respect the plan rate limit, and processes up to 100 URLs per run. A failure on one URL is captured in that URL's result and does not stop the remaining checks.
Redirects
1- Get Redirect Chain Traces the redirect chain for a URL and returns a flattened summary: every hop with its status code, latency and same origin or cross origin type, plus the final destination URL, its status code, the hop count and the total latency across the chain. Use this when you only need the redirect path rather than the full response from Check URL Status.
Frequently Asked Questions
What can FlowRunner do with HttpStatus?
FlowRunner agents can run Check URL Status, Get Redirect Chain, and Check URLs In Bulk in HttpStatus.
Does connecting HttpStatus to FlowRunner require OAuth?
No. HttpStatus connects to FlowRunner with an API key, no OAuth flow required.
Can HttpStatus trigger a FlowRunner workflow automatically?
HttpStatus doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with HttpStatus
$100 in credits. No card required. Connect in minutes.