op: submit
Submit a follow-up intent (invoke another action).
Allowed phases
| Phase | Status |
|---|---|
preflight | ✗ forbidden |
core | ✗ forbidden |
side_effects | ✓ allowed |
Syntax
- op: submit
intent_type: DELIVER_CHECKIN_NOTIFICATION
payload:
user_id: event.user_id
show_id: event.show_id
- op: submit
intent_type: INCREMENT_ARTIST_FOLLOWERS
target_entity: event.artist_id
payload:
artist_id: event.artist_id
user_id: event.user_idParameters
| Field | Required | Description |
|---|---|---|
intent_type | yes | Target action name (SCREAMING_SNAKE_CASE) |
payload | yes | Input map for the target action |
target_stream | no | Stream override |
target_entity | no | Entity ID expression on the target stream |
Behavior
- Side effects only. Submitted intents run asynchronously after the parent intent completes.
- Preferred pattern for cross-entity writes instead of cross-stream
setin core.
Related operations
See also
- Operations index — all ops by phase
- actions — rule structure and phases
- Intents: Rules — narrative examples