List Gotify Applications: Gotify 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
Client Token clientToken	string	Required	Client token (different from app token)

Sample request

{
  "clientToken": "{{trigger.clientToken}}"
}

Returns

[
  {
    "id": 1,
    "name": "Server",
    "token": "tok_abc",
    "description": "Backups"
  }
]

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

FAQ

Questions about List Gotify Applications.

What does the List Gotify Applications action do in Gotify?

Returns every Gotify application (sender identity) on the server. Useful for resolving app tokens and for inventorying notification senders.

What inputs does List Gotify Applications require?

Required: Client Token. 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 Gotify 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 List Gotify Applications support batch operations?

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

More actions