Look up an HTTP status codeLook up what an HTTP status code means and whether HTTP Cats has a cat for it: the name, the class (4xx client error, 5xx server error), whether an RFC defines it or a vendor made it up, and the picture, page and embed links. This is the one action that answers for any code from 100 to 599 rather than failing on one the site has no cat for: it reports the code as unknown, the nearest codes it does have, and the cat for the code's class, so a workflow can branch on whatever an HTTP step got back.
List HTTP status codesList the 78 HTTP status codes HTTP Cats has a cat for, each with its name, class, whether an RFC defines it, and the picture, page and embed links. Keep to one class, such as the 4xx client errors, or to the standard codes only. Nothing is fetched: the catalogue is the site's own published table, copied here, so the list is instant and the total is always reported.
Search HTTP status codesFind the HTTP status codes whose name contains a word, best match first: a name that is the word, then names that start with it, then names with a word that starts with it, then the rest, so 'time' leads with Request Timeout before Connection Timed Out. The first digits of a code work too: '50' finds every 50x code and '5xx' the whole class. Nothing is fetched, and the total number of matches is always reported.
Build a status cat URLTurn an HTTP status code into the address of its cat, ready to drop into a Slack alert, an email, an incident note or a README, with ready-made HTML and Markdown snippets beside it. Nothing is downloaded, so this is the cheap way to put a cat on a failed request. A code the site has no cat for fails the step and names the nearest codes it has, unless the class's cat is allowed instead, in which case 520 gets the 500 cat and the result says so.
Download a status catDownload the cat for an HTTP status code as a JPEG file, so a later step can attach it to an email, post it into a chat or put it in storage. Use this where a link will not do and the picture has to travel with the message. A code the site has no cat for fails the step and names the nearest codes it has, unless the class's cat is allowed instead.
Get a status cat as a data URIGet the cat for an HTTP status code inline, as a data URI rather than a link or a file, for somewhere that renders HTML but will not fetch a remote picture: an email whose images are blocked by default, a self-contained report, a page a later step builds. The pictures are JPEGs of a few tens of kilobytes, so the value is a long one; keep it for where a link cannot go.
Get a random status catPick one of the 78 HTTP cats at random, from the whole catalogue or from one class, for a cat of the day, a channel mascot or a stand-up opener. Give a seed to get the same cat every time for that seed: seed with the date and a daily post that retries, or that two people run an hour apart, picks the same cat, while tomorrow picks a different one. Nothing is downloaded; the result carries the links and embed snippets.
Check service statusCheck whether HTTP Cats is up and serving pictures, and how quickly. This is the one action that reports a problem as a value instead of failing the step, so a workflow can decide what to do about it. Being reachable but answering with something other than a picture is reported separately from being down.
