Moderate Text: OpenAI action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Text to Moderate input	string	Required	Text to Moderate
Model model	options	Optional	Model. Options: Omni Moderation (Latest), Text Moderation (Latest)

Sample request

{
  "input": "{{trigger.input}}",
  "model": "{{trigger.model}}"
}

Returns

{
  "id": "modr-abc",
  "model": "omni-moderation-latest",
  "results": [
    {
      "flagged": false,
      "categories": {
        "hate": false,
        "violence": false
      },
      "category_scores": {
        "hate": 0.0001
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Moderate Text.

What does the Moderate Text action do in OpenAI?

Checks text against OpenAI's moderation endpoint for harmful content (hate, harassment, self-harm, sexual, violence), with per-category scores. Free to use; gate user-generated content with this.

What inputs does Moderate Text require?

Required: Text to Moderate. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if OpenAI returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Moderate Text support batch operations?

Yes. Run Moderate Text inside a Loop node to process arrays. Tiny Command handles OpenAI's rate limits automatically so you don't have to throttle manually.

More actions