Magidoc

CreateActionCrmTaskInput
Input Object

Input type for creating a journey node that creates a CRM task for a contact in an integration partner's platform

Fields

#

accountIntegrationId

Optional: ID of the account integration

activityTypeId

Optional: ID of the activity type used by some integrations

assignedTo

Optional user ID to assign the task to. If not provided, will be assigned to the current user

calendarId

Optional: ID of the calendar. If no calendar is provided, the default calendar will be used.

description

Optional detailed description of the node's configuration or purpose. Useful for documenting complex logic or conditions. Max length: 255

dueDateUtc

The due date (in UTC using 'yyyy/M/dd' or expression) for the task

filter

Optional filter conditions that control node execution. For entry triggers: only contacts meeting these conditions can start the journey. For exit triggers: only contacts meeting these conditions will exit the journey. For other nodes: contacts not meeting these conditions will skip the node. If null, no filtering is applied and all contacts will process through the node normally.

integrationPartnerId

Optional: ID of the integration partner.

journeyId

Non-null

The unique identifier of the journey this node will be added to. Required to associate the node with a specific journey.

name

Optional display name for the node shown in the journey builder interface. Helps identify the node's purpose at a glance. Max length: 100

nextNodeId

Optional ID of the node that contacts should flow to after this node. Establishes the forward path in the journey flow.

previousNodeIds

Optional list of node IDs that should connect to this node as their next step. Used to establish the flow from existing nodes to this new node.

taskDescription

The task description

taskName

The task name. This is required for the node's IsConfigured to be true.

terminatorType

Specifies whether this trigger node starts or exits a journey. Only used for 'Trigger' type nodes. Entry triggers begin a journey when conditions are met, while exit triggers remove contacts from the journey.

Usages

#

References

#

  • Argument input of field createJourneyActionCrmTask from type Mutation