Create Bitlink activity

An activity that creates Bitlink, or short URL, from your long URL with Bitly.

Configure the Create Bitlink activity

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

To send an e-mail notification, click Advanced > E-mail Notifications .
For more information, refer to Configure E-mail Notifications for Any Activity.
In most text fields, you can use process data variables as an alternative to literal data values.
Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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?

On the Application Explorer screen, do one of these:
- Open a Process.
- Create a Process.
Do one of these:
- Add an activity:
  1. In the Process Builder, in the Activity Library, open the Bitly tab.
  2. On the Bitly tab, drag the Create Bitlink activity onto your process.
- Change an activity:
  1. In your process, double-click your activity.

Specifies the basic settings for the Create Bitlink activity.

Field Name	Definition
Display Name	Function: Specifies the activity name that shows in your process. Accepted Values: One line of text that can have spaces. Default Value: None Accepts Process Data 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	Function: Specifies an optional text description for your activity. Accepted Values: More than one line of text. Default Value: None Accepts Process Data Variables: No

Field Name

Definition

Display Name

Function:

Specifies the activity name that shows in your process.

Accepted Values:

One line of text that can have spaces.

Default Value:

None

Accepts Process Data 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

Specifies a long URL to change to a Bitlink, or short URL.

Field Name	Definition
Bitly	Function: Specifies the access token that connects to your Bitly environment. Accepted Values: A list of access tokens configured for your environment. Default Value: None Accepts Process Data Variables: No
Add Token	Opens this Screen: Access Token for Bitly Function of this Screen: Configure an access token to connect to Bitly..
Long URL	Function: Specifies a long URL to change to a Bitlink, or short URL. Accepted Values: A string in URL format. Default Value: None Accepts Process Data Variables: Yes
Store Short URL Response to this Variable	Function: Specifies a process data variable that stores the short URL that is associated with the specified Bitly account. Accepted Values: A process data variable. Default Value: None Accepts Process Data Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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?