Fire a custom trigger with payload
Changed onInvoke a custom trigger directly with an arbitrary JSON payload.
Fan-out: a trigger may be referenced by multiple flows (workflows). Firing it enqueues one execution per enabled, non-deleted flow attached to this trigger, each receiving the same payload. The enqueuedCount in the response reports how many were enqueued (0 if no flows are attached, or if all matching flows are gated by a cooldown).
Payload validation:
- If the trigger has a customPayloadSchema, the payload is validated against it (JSON Schema).
- If no schema is configured, the payload only needs to be a JSON object — any keys and values are accepted.
Only triggers with activation = "custom" can be fired through this endpoint; event and schedule triggers return 409.
Supports an optional Idempotency-Key header (1-255 printable ASCII characters), which maps to the derived invocationId used for fan-out deduplication. The payload is bound to the key on the first accepted fire, before fan-out. A repeat with the same key and an identical payload returns 202 with Idempotent-Replayed: true (deduplicated: true when flows were skipped; enqueuedCount counts only executions enqueued by that call); a changed payload under the same key returns 422 idempotency_key_reused.
Request
- Base URLhttps://api.mobilerun.ai
- URLhttps://api.mobilerun.ai/triggers/{triggerId}/fire
- AuthHTTP bearer
Path parameters
Headers
Idempotency-Key: 1-255 printable ASCII characters. Same key with a different request body is a 422 idempotency_key_reused. A retryable in-flight duplicate is a 409 with Retry-After and x-should-retry: true; a terminal duplicate is a 409 with x-should-retry: false. A replay returns the current resource state with Idempotent-Replayed: true.
Request body
Response
Custom trigger fired; one execution enqueued per enabled flow attached to this trigger
Changes
- breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - info
added the new optional
headerrequest parameteridempotency-key - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status
- breaking
- info
endpoint added
- info