MA
Interact with DECA MA (Marketing Action) to manage marketing actions.
Actions
Steps this node can perform. Add one from Add a step, then pick the action.
List Projects
Get a list of all projects under the organization
Settings
No settings.
Output
Later steps use this data by picking this step in the $ picker. For example, created_at is $.<step ID>.output.created_at.
{
"created_at": "string",
"id": "string",
"name": "string",
"organization_id": "string",
"settings": {},
"updated_at": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
created_at | Text | Timestamp when the project was created |
id | Text | Unique identifier for the project |
name | Text | Project name |
organization_id | Text | Organization identifier |
settings | Object | Project settings |
updated_at | Text | Timestamp when the project was last updated |
List Segments
Get a list of all segments
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier to filter segments |
| Search | Text | Search term to filter segments | |
| Sort | Text | Sort order (e.g., -id for descending by ID) Default: -id | |
| Page | Number | Page number for pagination Default: 1 | |
| Per Page | Number | Number of items per page Default: 30 |
Output
Later steps use this data by picking this step in the $ picker. For example, auto_update_flag is $.<step ID>.output.auto_update_flag.
{
"auto_update_flag": false,
"conditions": [],
"conditions_combination": "string",
"created_at": "string",
"id": "string",
"matched_type": "matched_all",
"name": "string",
"updated_at": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
auto_update_flag | Yes / No | Whether the segment auto-updates |
conditions[] | List | Segment conditions |
conditions_combination | Text | How conditions are combined |
created_at | Text | Timestamp when the segment was created |
id | Text | Unique identifier for the segment |
matched_type | Text | Type of matching (e.g., matched_all, matched_any) |
name | Text | Segment name |
updated_at | Text | Timestamp when the segment was last updated |
Create Segment
Create a new segment
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier |
| Data | Code | Yes | Segment data payload |
Output
Later steps use this data by picking this step in the $ picker. For example, auto_update_flag is $.<step ID>.output.auto_update_flag.
{
"auto_update_flag": false,
"conditions": [],
"conditions_combination": "string",
"created_at": "string",
"id": "string",
"matched_type": "matched_all",
"name": "string",
"updated_at": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
auto_update_flag | Yes / No | Whether the segment auto-updates |
conditions[] | List | Segment conditions |
conditions_combination | Text | How conditions are combined |
created_at | Text | Timestamp when the segment was created |
id | Text | Unique identifier for the segment |
matched_type | Text | Type of matching (e.g., matched_all, matched_any) |
name | Text | Segment name |
updated_at | Text | Timestamp when the segment was last updated |
List CRM Views
Get a list of CRM views
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier to filter CRM views |
Output
Later steps use this data by picking this step in the $ picker. For example, deca_org_id is $.<step ID>.output.deca_org_id.
{
"deca_org_id": "string",
"id": "string",
"name": "string",
"object_id": "string",
"object_name": "string",
"workspace_id": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
deca_org_id | Text | DECA organization ID |
id | Text | Unique identifier for the CRM view |
name | Text | CRM view name |
object_id | Text | Object ID |
object_name | Text | Object name |
workspace_id | Text | Workspace identifier |
List Marketing Actions
Get a list of marketing actions, optionally filtered by name, type, status, target segment, and date range.
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier to filter marketing actions |
| Action Name | Text | Filter by action name (partial match — case-sensitive contains). | |
| Action Type | Choice | Filter by marketing action type. Use Rich Menu to find the active LINE Rich Menu campaign for a segment. Options: Rich Menu, Popup, Notification, Chatbot, Inflow, External, Webhook Message | |
| Status | Choice | Filter by publication status. Options: Draft, Pending Approval, Active, Suspended, Rejected, Expired | |
| Target Segment ID | Text | Filter actions targeting this segment ID (matches when the segment is a member of the action's target_segments). | |
| Start From | Date and time | Returns actions whose start_at is on or after this date/time. | |
| Start To | Date and time | Returns actions whose start_at is on or before this date/time. | |
| Expect Exactly One Result | Yes / No | When enabled, the action fails if zero or more than one matching action is returned. Use this for unique-action lookups (e.g., the active Rich Menu for a specific segment). Default: false |
Output
Later steps use this data by picking this step in the $ picker. For example, created_at is $.<step ID>.output.created_at.
{
"created_at": "string",
"description": "string",
"end_at": "string",
"id": "string",
"marketing_action_type": {},
"marketing_action_type_id": 0,
"organization_id": "string",
"project_id": "string",
"settings": {},
"start_at": "string",
"status": "string",
"target_segments": [],
"updated_at": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
created_at | Text | Timestamp when the marketing action was created |
description | Text | Marketing action description |
end_at | Text | End time of the marketing action |
id | Text | Unique identifier for the marketing action |
marketing_action_type | Object | Marketing action type details |
marketing_action_type_id | Number | ID of the marketing action type |
organization_id | Text | Organization identifier |
project_id | Text | Project identifier |
settings | Object | Marketing action settings |
start_at | Text | Start time of the marketing action |
status | Text | Status of the marketing action |
target_segments[] | List | Target segments for the marketing action |
updated_at | Text | Timestamp when the marketing action was last updated |
Create Marketing Action
Create a new marketing action
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier |
| Data | Code | Yes | Marketing action data payload |
Output
Later steps use this data by picking this step in the $ picker. For example, created_at is $.<step ID>.output.created_at.
{
"created_at": "string",
"description": "string",
"end_at": "string",
"id": "string",
"marketing_action_type": {},
"marketing_action_type_id": 0,
"organization_id": "string",
"project_id": "string",
"settings": {},
"start_at": "string",
"status": "string",
"target_segments": [],
"updated_at": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
created_at | Text | Timestamp when the marketing action was created |
description | Text | Marketing action description |
end_at | Text | End time of the marketing action |
id | Text | Unique identifier for the marketing action |
marketing_action_type | Object | Marketing action type details |
marketing_action_type_id | Number | ID of the marketing action type |
organization_id | Text | Organization identifier |
project_id | Text | Project identifier |
settings | Object | Marketing action settings |
start_at | Text | Start time of the marketing action |
status | Text | Status of the marketing action |
target_segments[] | List | Target segments for the marketing action |
updated_at | Text | Timestamp when the marketing action was last updated |
Create Marketing Action (Normal Message)
Create a new marketing action with normal message
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Data | Object | Marketing action data payload |
Output
Later steps use this data by picking this step in the $ picker. For example, created_at is $.<step ID>.output.created_at.
{
"created_at": "string",
"description": "string",
"end_at": "string",
"id": "string",
"marketing_action_type": {},
"marketing_action_type_id": 0,
"organization_id": "string",
"project_id": "string",
"settings": {},
"start_at": "string",
"status": "string",
"target_segments": [],
"updated_at": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
created_at | Text | Timestamp when the marketing action was created |
description | Text | Marketing action description |
end_at | Text | End time of the marketing action |
id | Text | Unique identifier for the marketing action |
marketing_action_type | Object | Marketing action type details |
marketing_action_type_id | Number | ID of the marketing action type |
organization_id | Text | Organization identifier |
project_id | Text | Project identifier |
settings | Object | Marketing action settings |
start_at | Text | Start time of the marketing action |
status | Text | Status of the marketing action |
target_segments[] | List | Target segments for the marketing action |
updated_at | Text | Timestamp when the marketing action was last updated |
Get Marketing Action
Fetch a single marketing action by ID, including full settings (e.g., Rich Menu IDs published to LINE under settings.line_rich_menus).
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier |
| Marketing Action ID | Text | Yes | ID of the marketing action to fetch. Typically wired from a previous List Marketing Actions node. |
Output
Later steps use this data by picking this step in the $ picker. For example, created_at is $.<step ID>.output.created_at.
{
"created_at": "string",
"description": "string",
"end_at": "string",
"id": "string",
"marketing_action_type": {},
"marketing_action_type_id": 0,
"organization_id": "string",
"project_id": "string",
"settings": {},
"start_at": "string",
"status": "string",
"target_segments": [],
"updated_at": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
created_at | Text | Timestamp when the marketing action was created |
description | Text | Marketing action description |
end_at | Text | End time of the marketing action |
id | Text | Unique identifier for the marketing action |
marketing_action_type | Object | Marketing action type details |
marketing_action_type_id | Number | ID of the marketing action type |
organization_id | Text | Organization identifier |
project_id | Text | Project identifier |
settings | Object | Marketing action settings |
start_at | Text | Start time of the marketing action |
status | Text | Status of the marketing action |
target_segments[] | List | Target segments for the marketing action |
updated_at | Text | Timestamp when the marketing action was last updated |
Upload CSV Segment
Upload a new segment from CSV data
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier |
| CSV Data | Code | Yes | CSV data - can be either raw CSV text (with headers) or an array of objects that will be converted to CSV format. When using array format, data from previous nodes (e.g., parsed CSV files) can be directly passed. (Format: email,phone,lineId,TEXT_COLUMN1,TEXT_COLUMN2,TEXT_COLUMN3,TEXT_COLUMN4,TEXT_COLUMN5) Default: email,phone,lineId,TEXT_COLUMN1,TEXT_COLUMN2,TEXT_COLUMN3,TEXT_COLUMN4,TEXT_COLUMN5 a@b.com,,Ua74c67bdb611a4dc9470d41ddc00000c,,,,, |
Output
Later steps use this data by picking this step in the $ picker. For example, file_name is $.<step ID>.output.file_name.
{
"file_name": "string",
"key": "string",
"name": "string",
"segment": "csv",
"status": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
file_name | Text | Name of the uploaded CSV file |
key | Text | S3 key for the uploaded CSV file |
name | Text | Display name of the CSV segment upload |
segment | Text | Type of segment (e.g., csv) |
status | Text | Status of the CSV segment upload operation |
List Libero Labels
Get a list of all Libero labels
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier to filter Libero labels |
Output
Later steps use this data by picking this step in the $ picker. For example, [0].group is $.<step ID>.output.[0].group.
[
{
"group": {},
"id": "string",
"name": "string",
"source": "string",
"type": "string"
}
]Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
group | Object | Group of the Libero label |
id | Text | Unique identifier for the Libero label |
name | Text | Name of the Libero label |
source | Text | Source of the Libero label |
type | Text | Type of the Libero label |
Generate Segmentation File Upload URL
Generate a presigned URL for uploading segmentation files to S3 storage
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier |
Output
Later steps use this data by picking this step in the $ picker. For example, key is $.<step ID>.output.key.
{
"key": "string",
"presigned_url": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
key | Text | S3 object key for the file |
presigned_url | Text | Presigned URL for file upload |
Initialize Segmentation File Processing
Initialize segmentation file processing job after uploading to S3
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier |
| S3 Key | Text | Yes | S3 object key of the uploaded segmentation file |
| Job Type | Text | Yes | Type of segmentation processing job to initiate Default: upload_target_csv |
| Target Segment Group | Text | Target segment group for the segmentation file processing Default: include | |
| Target Segment Type | Text | Target segment type for the segmentation file processing Default: csv |
Output
Later steps use this data by picking this step in the $ picker. For example, job_id is $.<step ID>.output.job_id.
{
"job_id": "string",
"message": "string",
"status": "success"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
job_id | Text | Unique identifier for the processing job |
message | Text | Additional information about the job status |
status | Text | Status of the file processing job (e.g., success, processing, failed) |
Aggregation Report
Get an aggregation report
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier |
| Marketing Action ID | Text | Marketing Action ID | |
| Target Segment | Text | Target segment | |
| Delivery Type | Text | Delivery type Default: notification | |
| Device Type | Text | Device type | |
| From (Format: 2025-11-27T17:00:00.633Z) | Text | Yes | From (Format: 2025-11-27T17:00:00.633Z) |
| To (Format: 2025-11-27T17:00:00.633Z) | Text | Yes | To (Format: 2025-11-27T17:00:00.633Z) |
Output
Later steps use this data by picking this step in the $ picker. For example, aggregation_end is $.<step ID>.output.aggregation_end.
{
"aggregation_end": "string",
"aggregation_start": "string",
"alias": "string",
"click_uu": 0,
"cv_amount": 0,
"cv_type": "string",
"cv_uu": 0,
"delivery_uu": 0,
"description": "string",
"display_uu": 0,
"marketing_action_id": "string",
"notification_type": "string",
"open_uu": 0,
"optout_uu": 0,
"organization_id": "string",
"project_id": "string",
"use_uu": 0
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
aggregation_end | Text | Aggregation end |
aggregation_start | Text | Aggregation start |
alias | Text | Marketing Action Alias |
click_uu | Number | Click UU |
cv_amount | Number | Conversion Amount |
cv_type | Text | Conversion type |
cv_uu | Number | Conversion UU |
delivery_uu | Number | Delivery UU |
description | Text | Description |
display_uu | Number | Display UU |
marketing_action_id | Text | Marketing Action ID |
notification_type | Text | Notification type |
open_uu | Number | Open UU |
optout_uu | Number | Optout UU |
organization_id | Text | Organization identifier |
project_id | Text | Project identifier |
use_uu | Number | Use UU |
Delivery Status Report
Get a delivery status report
Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Project ID | Text | Yes | Project identifier |
| Marketing Action ID | Text | Yes | Marketing Action ID |
Output
Later steps use this data by picking this step in the $ picker. For example, aggregation_time is $.<step ID>.output.aggregation_time.
{
"aggregation_time": "string",
"error": "string",
"marketing_action_description": "string",
"marketing_action_id": "string",
"organization_id": "string",
"project_id": "string",
"reserved": "string",
"sent": "string"
}Example values show the shape of the data, not real values. See Using data from earlier steps.
Field descriptions
| Field | Type | Description |
|---|---|---|
aggregation_time | Text | Aggregation time |
error | Any | |
error.email | Number | Number of Emails |
error.line | Number | Number of Line messages |
error.sms | Number | Number of SMS |
marketing_action_description | Text | Marketing Action Description |
marketing_action_id | Text | Marketing Action ID |
organization_id | Text | Organization identifier |
project_id | Text | Project identifier |
reserved | Any | |
reserved.email | Number | Number of Emails |
reserved.line | Number | Number of Line messages |
reserved.sms | Number | Number of SMS |
sent | Any | |
sent.email | Number | Number of Emails |
sent.line | Number | Number of Line messages |
sent.sms | Number | Number of SMS |