Create Card activity

An activity that creates a card in Trello.


Create Card activity

Configure the Create Card activity

To configure the Create Card activity, do the procedure in this topic.

Prerequisites

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library, open the Trello tab.

    Open Trello tab
  3. On the Trello tab, drag the Create Card activity onto your process.

    Drag Create Card activity

General Configuration

Specifies the basic settings for the Create Card activity.

Figure: General Configuration screen

General Configuration screen

Good to Know

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

Fields

Field NameDefinition

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

Create Card

Specifies the information about the card that you want to create in Trello.

Figure: Create Card Configuration > Configuration tab

Create Card Configuration Configuration tab

Fields

Field NameDefinition

Trello

Description:
Specifies the access token that connects to your Trello service.
Allowed Values:
A list of access tokens configured for your environment.
Default Value:
None

Create Create icon

Opens this Screen:
Access Token for Trello
Function of this Screen:
Configure an access token to connect to Trello.

Team

Description:
Specifies the team for which to create the new card.
Allowed Values:
A valid team name in Trello.
Default Value:
None

Board

Description:
Specifies the board for which to create the card.
Allowed Values:
A valid board name in Trello.
Default Value:
None
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?

List

Description:
Specifies the list for which the new card will be created.
Allowed Values:
A valid list name in Trello.
Default Value:
None
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?

Card Name

Description:
Specifies the name for the card.
Allowed Values:
A valid card name in Trello.
Default Value:
None
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?

Position

Description:
Specifies where the card shows on the board.
Allowed Values:
  • Bottom
  • Top
Default Value:
None

User Names

Description:
Specifies the names of the users for whom to create the new card.
Allowed Values:
A valid user name or display name of the member in Trello.
Default Value:
None
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?

Due Date

Description:
Specifies the reference date for your date calculation.
Allowed Values:
  • Custom Attributes - Specifies a process data variable that stores the date-time value and your date-time format.

    You can use App Data screen to specify a process data variable.

    You can also use a custom date-time format. For more information, refer to Customize Your Date-Time Format.

  • Static - Specifies a static date and time.
  • Now - The date and time the system activity starts at runtime.
Default Value:
None

Make Due Date as Completed

Description:
Specifies if the task is due or completed.
Allowed Values:
  • Selected - Shows that the task is completed.
  • Deselected - Shows that the task is due.
Default Value:
Deselected

Create Card Configuration > Description tab

Specifies information about the card in Trello.

Figure: Create Card Configuration > Description tab

Create Card Configuration Description tab
Field NameDefinition

Card Description

Description:
Specifies information about the card in Trello.
Allowed Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None

Create Card Configuration > Response tab

Configures the response settings for a Trello card.

Figure: Create Card Configuration > Response tab

Create Card Configuration Response tab
Field NameDefinition

Response ID

Description:
Specifies a process data variable to store the ID associated with the card in Trello.
Allowed Values:
A process data variable.
Default Value:
None
Accepts Variables:
Yes
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?

Response URL

Description:
Specifies a process data variable to store the URL that opens your card in Trello.
Allowed Values:
A process data variable.
Default Value:
None
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?