Search Mattermost Posts: Mattermost 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
Team ID team_id	string	Required	The Team ID assigned by Mattermost. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Search Terms terms	string	Required	—
OR Search is_or_search	options	Optional	—

Sample request

{
  "team_id": "{{trigger.team_id}}",
  "terms": "{{trigger.terms}}",
  "is_or_search": "{{trigger.is_or_search}}"
}

Returns

{
  "order": [
    "post_abc"
  ],
  "posts": {
    "post_abc": {
      "id": "post_abc",
      "message": "Found",
      "user_id": "user_abc"
    }
  }
}

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

FAQ

Questions about Search Mattermost Posts.

What does the Search Mattermost Posts action do in Mattermost?

Full-text search with channel and date filters. For "find posts mentioning X" archive-search workflows.

What inputs does Search Mattermost Posts require?

Required: Team ID, Search Terms. 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 Mattermost 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 Search Mattermost Posts support batch operations?

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

More actions