Get Long URL
Use the Get Long URL action to retrieve the original long URL associated with the specified Bitlink.
Complete the following steps to use the Get Long URL action in your workflow:
1. Drag the Get Long URL action under Bitly to the canvas, place the pointer on the action, and then click 
or double-click the action. The Get Long URL window opens.
or double-click the action. The Get Long URL window opens.2. Edit the Label, if needed. By default, the label name is the same as the action name.
3. To add a Bitly connector type, refer to Supported Bitly Connector Types.
If you previously added a connector type, select the appropriate Connector Type, and under Connector Name, select the connector.
4. Click TEST to validate the connector.
5. Click MAP CONNECTOR to execute the action using a connector that is different from the one that you are using to populate the input fields. In the Runtime Connector field, provide a valid Bitly connector name. For more information about MAP CONNECTOR, see Using Map Connector.
6. In the Specify Link Using list, select how you want to specify the link, and perform its respective task:
Specify Link Using | Task |
|---|---|
Bitlink | In the Bitlink field, enter the Bitlink for which you want to retrieve details. |
Id | In the Id field, enter the ID of the link for which you want to retrieve details. |
 | v1 of the Get Long URL action supported multiple Bitlinks as input. The current version, v2 supports a single Bitlink or Id in the input. |
7. Under the Additional Fields group, click Add, and do the following:
a. In the Field Name field, enter the UI field name of the Bitly service that you want to add. The field name should be the same as name specified in the API documentation.
b. In the Value field, enter the value of the field.
Click Add to add multiple fields and values. Click 
to delete any field values that you added.
to delete any field values that you added.8. Click Done.
Output schema
| | In some cases, the output of the Get Long URL action shows incorrect protocol of the Bitlink. This is an issue with the Bitly expand API. |