Update Item (Monday) activity

An activity that changes an item in a Monday group.

Configure the Update Item activity

Examples

(External) AgilePoint NX Connector For Monday.
Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Prerequisites

AgilePoint NX OnDemand (public cloud), or AgilePoint NX PrivateCloud or AgilePoint NX OnPremises v9.0 Software Update 1 or higher.

Good to Know

To send an email notification, click Advanced > Email Notifications .
For more information, refer to Email Notifications screen (Process Activities).
In most text fields, you can use process data variables as an alternative to literal data values.
You can configure whether this activity waits for other activities before it runs.
For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?
This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

How to Start

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, open the Monday tab.
On the Monday tab, drag the Update Item activity onto your process.

General Configuration

Specifies the basic settings for the Update Item activity.

Good to Know

Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field Name	Definition
Display Name	Description: Specifies the activity name that shows in your process. Allowed Values: One line of text (a string). Accepted: Letters Numbers Spaces Default Value: None Accepts Variables: No Example: This is a common configuration field that is used in many examples. Refer to: Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.
Description	Description: Specifies an optional text description for your activity. Allowed Values: More than one line of text. Default Value: None Accepts Variables: No

Field Name

Definition

Display Name

Description:

Specifies the activity name that shows in your process.

Allowed Values:

One line of text (a string).

Accepted:

Letters
Numbers
Spaces

Default Value:

None

Accepts Variables:

Example:

This is a common configuration field that is used in many examples. Refer to:

Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Description:: Specifies an optional text description for your activity.
Allowed Values:: More than one line of text.
Default Value:: None
Accepts Variables:: No

Update Item Configuration

Specifies the information to change an item in a Monday group.

Fields

Field Name	Definition
Monday	Description: Specifies the access token that connects to Monday. Allowed Values: A list of access tokens configured for your environment. Default Value: None Example: Refer to: (External) AgilePoint NX Connector For Monday
Create	Opens this Screen: Access Token for Monday Function of this Screen: Configure an access token to connect to Monday.
Workspace Name Or ID	Description: Specifies the name or ID of the workspace in which to change the item. Allowed Values: A workspace name from the list. When you select the access token from the Monday field, this field shows the workspace names associated with the access token. An integer that represents a workspace ID. The workspace ID comes from Monday. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Monday Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Board ID	Description: Specifies the name or ID of the board in which to change an item . Allowed Values: A board name from the list. When you specify the workspace name or workspace ID in the Workspace Name Or ID field, this field shows the board names associated with the workspace. An integer that represents a board ID. The board ID comes from Monday. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Monday Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Item ID	Description: Specifies the ID of the item to change. The item ID comes from Monday. Allowed Values: An item ID from Monday. Default Value: None Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Monday Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Map Request To App Schema / Map Payload To App Schema	Description: Specifies how to connect the request data from Monday to the AgilePoint process schema. Allowed Values: Map Request To App Schema - Connects the Monday API request parameter to your process schema. Click Map Request To App Schema to open the Schema Mapper. Use this screen to connect the response to the data model for your process. Map Payload To App Schema - Specifies a payload to create an item. The payload must be in JSON or XML format. Click the Map Schema button to open the Schema Mapper. Use this screen to connect the payload values to the AgilePoint process schema. Default Value: Map Request To App Schema Accepts Variables: Yes Example: Refer to: (External) AgilePoint NX Connector For Monday Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?