Welcome

4.0

Welcome provides marketing management software & content marketing services to marketing teams who want to elevate performance.

Overview

Copy

Supercharge your team's ability to plan, execute, and manage exceptional campaigns and content, and elevate the performance of marketing with marketing management software and content marketing services from Welcome.

Authentication

Copy

Within the workflow builder, highlight the Welcome connector.

In the Welcome connector properties panel to the right of the builder, click on the Authenticate tab and the 'Add new authentication' button.

This will result in a Tray.io authentication pop-up modal. The first page will ask you to name your authentication and select the type of authentication you wish to create ('Personal' or 'Organisational').

The next page asks you for your 'Client ID' and 'Client Secret' credentials.

In order to get these fields, head to the Welcome dashboard. Click on your username logo in the navigation bar and select the 'App & Webhooks' option from the side menu which appears.

To get the 'Client ID' and 'Client Secret' credentials, click on your app.

They are listed under the 'Apps' tab.

Once you have added these fields to your Tray.io authentication pop-up window, click the 'Create authentication' button.

Go back to your settings authentication field (within the workflow builder properties panel), and select the recently added authentication from the dropdown options now available.

Your connector authentication setup should now be complete.

Welcome Trigger

Copy

If you wish your workflow to be kicked off by a particular action in Welcome, you can use the Welcome Trigger.

The Welcome trigger allows you to receive notifications and trigger workflows when given events occur associated with the selected trigger operation.

Trigger Operations available:

Copy

• Asset added

• Asset removed

• Asset modified

Webhook Setup

Copy

Select the Welcome trigger. This can be done either at the create new workflow stage or updated within the workflow builder itself.

Highlight the Welcome trigger. In the Welcome trigger properties panel to the right of the builder, click on the Authenticate tab and the 'Add new authentication' button.

At this stage, you can create a new authentication using the steps specified in the Authentication section above.

Or you can select the already created authentication from the available list.

To finish setting up your trigger you will need to register the trigger through the Welcome API under the previous 'Apps & Webhooks' section of the Welcome dashboard.

Click the 'Register a Webhook' button. The next page will ask you for the 'Callback URL' and 'Secret'. Leave these blank for now but save the page for later use.

To get your 'Callback URL' head back to your Tray builder, click the ellipses in the top left corner and click 'Workflow settings'.

Copy the 'Workflow public URL'.

Head back to your Welcome dashboard, and paste this into the 'Callback URL' field within the Apps and Webhook page.

The 'Secret' is created by you and must match the secret used when registering the webhooks. Enter your secret into the Welcome trigger section and be sure to tick all the events you want this webhook to listen to.

Lastly, to finish your trigger set up, head back to your workflow, enter your 'Secret', and click enable.

You can check the input and output for your trigger using the Debug tab.

Available Operations

Copy

The examples below show one or two of the available connector operations in use.

Please see the Full Operations Reference at the end of this page for details on all available operations for this connector.

Using the Raw HTTP Request ('Universal Operation')

Copy

As of version 1.0, you can effectively create your own operations.

This is a very powerful feature which you can put to use when there is an endpoint in Welcome which is not used by any of our operations.

To use this you will first of all need to research the endpoint in the Welcome API documentation v3.0, to find the exact format that Welcome will be expecting the endpoint to be passed in.

Note that you will only need to add the suffix to the endpoint, as the base URL will be automatically set (the base URL is picked up from the value you entered when you created your authentication).

The base URL for Welcome is: https://api.welcomesoftware.com/v3

For example, say that the 'Get Assets' operation did not exist in our Welcome connector, and you wanted to use this endpoint. You would use the Welcome API docs to find the relevant endpoint - which in this case is a GET request called: /assets.

More details about this endpoint can be found here.

As you can see, there is also the option to include a query parameter, should you wish to do so. So if you know what your method, endpoint, and details of your query parameters are, you can return a list of the images in your Welcome library with the following settings:

Method: GET

Endpoint: assets

Query Parameter: Key: type Value: image

Body Type : Raw : { "none" : "null" }

Final outcome being: https://api.welcomesoftware.com/v3/assets?type=image

Example Usage

Copy

Below is an example of a way in which you could potentially use the Welcome connector, to update an asset (for example your company's logo) within your Welcome library.

1. Setup using a manual trigger.

2. Download your chosen file from your Google Drive using the Google Drive connector.

3. Use the Welcome connector to update an existing asset in your Welcome library by uploading your file (downloaded in the previous step) as a new asset version.

4. Update your new asset version with additional information.

Your completed workflow should look similar to this:

1 - Setup Trigger & Download File from your Google Drive Account

Copy

Select the Manual trigger from the trigger options available.

From the connectors panel on the left, add a Google Drive connector to your workflow. Set the operation to 'Download file'.

As you can see, the 'File ID' field is required.

To get this field, navigate to your chosen image in your Google Drive account and click on the Hamburger icon (3 vertical dots) on the top right corner.

Next, select 'Share' from the navigation menu which appears and select the 'Copy link' option.

Your file ID can be found in the copied link URL, and will look like this: https://drive.google.com/file/d/yourfileid/view?usp=sharing

Feel free to re-name your steps as you go along to make things clearer for yourself and other users. The operation names themselves often suffice.

You have now configured your workflow to be manually triggered and to download a file from your Google Drive.

2 - Upload a New Asset Version

Copy

Next, search for the Welcome connector within your connector panel, and drag it into your workflow as your next step. Set your operations to 'Upload asset version'.

As you can see, the 'Asset ID', 'File', and 'Title' fields are required.

You can select the name of the file you wish to create a new version of from the drop-down list underneath 'Asset ID'.

Next, use the file mapping icon (found next to the File input field, within the properties panel) to generate the connector-snake.

While hovering over the 'Download file' step (with the tail end of the connector-snake), select file from the list of output properties displayed. This will auto-populate a jsonpath within your list input field, and update the type selector to jsonpath.

Finally, you can give your file a title - this can be whatever you want!

For more clarification on the pathways you have available, open the Debug panel to view your step's Input and Output.

If you head to your Welcome library, you will see that your existing file has now been updated with the new version you just uploaded.

3 - Update Asset Information

Copy

The last step is to drag another Welcome connector into your workflow. Set the operation to 'Update image'. As you can see, the 'ID' field is required.

In order to specify the image you want to update, start by using the ID mapping icon (found next to the ID input field, within the properties panel) to generate the connector-snake.

While hovering over the 'Upload asset version' step (with the tail end of the connector-snake), select asset_id from the list of output properties displayed. This will auto-populate a jsonpath within your list input field, and update the type selector to jsonpath.

Now that we have selected the correct asset, we want to give it some additional information.

You could give your asset a new title here, but as we already gave it a title in the previous step we will leave it empty.

To begin, select 'Add to Labels' underneath the 'Labels' input field. Next, pick an option from the drop-down list underneath the 'Group ID' input field.

Finally, select 'Add to Value IDs' and choose any of the options with the 'Group ID' you selected, prepending the option.

The end result in your UI should look something like this:

You have now successfully completed this tutorial, where you have learned how to download a file from Google Drive inside of a Tray workflow and use it to create a new asset version in your Welcome library.