Actionflow Node List
Nodes include database operations, AI execution, permission changes, API calls, code blocks, loops, conditions, and integrations.
Setup guide: Building Actionflows.
Database
Query, insert, update, and delete on a selected table.
Currently, a single database query node can retrieve a maximum of 1000 rows. For larger datasets, use loops to query in batches.
Call API
Run an API already configured under API, bind its response to output parameters, and expose the API result on the Actionflow.
Run AI
Run a configured Agent (set the Actionflow execution mode to asynchronous).
Run Actionflow
Call another Actionflow. A synchronous Actionflow cannot call an asynchronous one.
Set Variable
Assign values to declared Actionflow variables.
Current User
Get the current user ID and access token for the logged-in user.
Permissions
Grant or revoke roles for specific users.
Run Code
Run a custom code block; see Code Block Development.
Files
Save external images, videos, and files and convert them to Momen’s native types.
Condition
Add branch logic. Conditions are evaluated left to right.
Loop
Iterate over each item in a list and run the inner actions for every element. The loop works as follows:
- Input: This node receives a list as its data source.
- Execution: It starts from the first item, runs all actions inside the loop, then moves to the next item until the list is exhausted.
- Output: In each iteration, you can use item data (item) and item index (index) as input for inner nodes.
To loop a fixed number of times, use the SEQUENCE formula to build an array of the desired length and use it as the loop data source.
Condition Loop
Run a block of logic repeatedly while a condition is true. The loop works as follows:
- Condition: Set a condition expression.
- Execution: If the condition is true, run all actions inside the loop; otherwise exit the loop.
- End: The loop stops when the condition becomes false.
To prevent infinite loops, a single condition loop can run at most 100 times.
Break Loop
Exit the innermost active loop.
Gemini Veo 3.1
Video generation node. Veo 3.1 can generate up to ~8 seconds of high-fidelity 720p, 1080p, or 4K video with native audio (set the Actionflow execution mode to asynchronous).
Parameters
| Parameter | Description | Type | Required |
|---|---|---|---|
| prompt | Text prompt for the video. Supports audio prompts. | Text | Yes |
| negativePrompt | What the video should not contain. Cannot be used together with any referenceImage1, referenceImage2, or referenceImage3 input, or the call will fail. | Text | No |
| firstImage | First frame of the video. Cannot be used together with any reference image field (referenceImage1–3), or the call will fail. | Image | No |
| lastImage | Last frame of the video. Cannot be used together with any reference image field, must be used with firstImage, or the call will fail. | Image | No |
| referenceImage1/2/3 | Up to three reference images for style and content. If the matching referenceType is null, that slot has no effect. | Image | No |
| referenceType1/2/3 | Reference type: only "asset" or "style". "asset": reference provides material (scenes, objects, characters). "style": reference provides style (color, lighting, texture); at most one "style" image. If the matching referenceImage field is empty, that slot has no effect. | Text | No |
| aspectRatio | Only "16:9" (default) or "9:16". | Text | No |
| resolution | Only "720p", "1080p", or "4k"; default 720p. | Text | No |
| durationSeconds | Clip length in seconds; only 4, 6, or 8; default 8. | Integer | No |
| video | Generated video output. | Video | Yes |
Send SMS - Twilio
Twilio is a widely used cloud communications platform. This node sends SMS verification codes, international logistics notifications, and other text messages.
To use it for verification during sign in, sign up, reset password, bind/unbind account, or deregistration, add a custom configuration under Settings → Verification code and wire this node’s parameters in your custom send Actionflow. See User event collection – Send verification code.
1. Prerequisites (in the Twilio console)
- Account: Sign up and open the Twilio Console .
- Credentials: Copy Account SID and Auth Token (reveal the token before copying; keep it secret).
- From number: Purchase or use a trial Twilio number enabled for SMS; that value goes in
from_phone_number. Format must meet Twilio requirements (usually E.164 with country code, e.g.+12025550100).
2. Configure the node (in Momen)
The Inputs on the right map one-to-one to Twilio’s send API. See Twilio’s Message resource for limits and behavior.
-
account_sid
- How to fill: Account SID from Account Info in the Twilio console.
- Example:
ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-
auth_token
- How to fill: Auth Token for that account. Do not leak it or commit it to public repos.
-
from_phone_number
- How to fill: The Twilio number that sends SMS; must be SMS-enabled and allowed as a sender in your project.
- Example:
+12025550100
-
to_phone_number
- How to fill: Recipient mobile number.
- Example:
+13800138000
Both
from_phone_numberandto_phone_numbermust be E.164 (with+and country code), e.g.+13800138000, or sending may fail. -
message
- How to fill: Plain-text body. Length and segmentation follow carrier and Twilio rules—refer to Twilio docs and errors. When used with a custom verification Actionflow, typically concatenate the verification code from Actionflow inputs into the message body.