Chuck Norris Jokes

• Get a random jokeGet one random Chuck Norris fact, ready to post, with a link back to it. Narrow it to a category such as dev or movie, or leave the category empty to draw from the whole catalogue. Swap in a colleague's name to personalise it. Explicit facts are skipped unless you ask for them.
• Get random jokesGet several different Chuck Norris facts at once, up to 20, optionally all from one category. No fact is drawn twice in the same batch. The service returns one random fact per request, so a batch costs a request per fact and a little more; asking a small category for more than it holds returns what there is rather than failing.
• Get a joke by idGet one specific fact by its id, for re-posting a fact an earlier step found. Ids are opaque strings the service assigns once and never reuses, so an id stored last month still means the same fact. A full chucknorris.io joke URL is accepted in place of the bare id.
• Search jokesFind the facts that mention something, a name, a language or a place, best match first. The service publishes no relevance of its own, so matches are ranked here with a whole-word hit worth far more than one buried inside a longer word. Narrow to a category, and see how many explicit matches were left out. The query must be 3 to 120 characters, which is the service's own limit.
• Get joke categoriesList the categories a fact can be filtered by, each flagged for whether it is the adult one, so a step that builds a filter from this list can leave that one out without knowing its name in advance.
• Get the joke of the dayPick one fact for a day and keep picking that same fact all day. A random draw gives a different one on every call, so a daily workflow that retries, or that two people run an hour apart, posts two different facts for the one day. This one is fixed by the date: the same date always gives the same fact, and tomorrow gives a different one. Add a seed of your own to have two workspaces post different facts on the same day.
• Check service statusCheck whether chucknorris.io is answering, 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 throttled at the edge is reported separately from being down.

No actions match that.