Auth variables
Introduction
The auth variables tab is used to define authentication variables for any values that you need users to provide when they choose to add an instance of this connector, for use in process flows:
Here, you define what fields a user will be asked to complete when they choose to add an instance, select and authentication method, and provide credentials. For example:
You also define how any provided values are passed in authentication requests - i.e. are they included in the API request URL, the header, or the body?
Default auth variables
Having chosen an authentication method to configure, any required variables for that method are listed by default - for example:
These are variables that are always required to authenticate using this authentication method. You can't remove or change the behaviour of these variables, but you can change the display name if required.
Default auth variables are pre-configured to be passed into API requests as needed. For example, token-based authentication has one default parameter, which is pre-configured on the header tab. If your requirements are different, you can change how/where these variables are used.
Adding auth variables
To add an auth variable, follow the steps below:
Step 1 Start by selecting the connector variables tab to check if there are any instance-level variables for this connector that you want to include. Any variables defined for the instance as a whole are shown here - click the use button for any that you wish to include as an auth variable - for example:
When you choose to use a connector variable, you'll see that it gets added to the auth variables tab - for example:
Step 2 Back in the auth variables tab, you can now add any other variables for information that you need to provide when they add an instance of this connector with this authentication method. To do this, click the add variable button:
Step 3 Complete details and set options on the add variable page:
What can I enter here?
The API documentation for the underlying third-party application should provide guidance about what variables can/should be passed in authentication requests. The example below is from Shopify's API documentation:
The add variables page is the same for all types of variables that you may encounter in the connector builder (for information about these options please see the Working with variables page). However, it's worth noting the effect of setting required and configurable by user options in the context of auth variables:
When you add an auth variable and choose to make it required, you are effectively saying: 'When a user adds an instance of this connector, do not allow them to proceed without providing a value for this variable'.
When you add an auth variable and choose to make it only configurable by users, you are effectively saying: 'When a user adds an instance of this connector, allow them to provide a value for this variable if they have one but if they don't, let them proceed'.
Step 4: Click the save button.
Step 5 Having added a variable, make sure that you go on to define how any values captured for it should be passed in API requests. Typically, any user-provided variable that you define here would then be added to the authentication request URL path, authentication request URL parameters, the authentication request header, or the authentication request body for the authentication method.
How do I know where to put these variables?
The API documentation for the underlying third-party application should provide guidance about where/how authentication variables need to be passed in requests. The example below is from Shopify's API documentation:
If you add auth variables which require user-provided values but don't go on to add them to the authentication method's request URL path, header, or body the result will be that users are prompted to provide these details (if you chose to display these variable fields to users), but no action will be taken with that information.
Last updated