Change pipelines
In this article, we discuss changing your Quickbase pipelines to meet the upcoming security changes and help keep your data secure.
Note
This isn't a standard use case. We don't fully support using our extensions from pipelines unless explicitly stated for that specific extension. Submit a technical support case to check whether your use case is a valid way to use one of our extensions. More often than not, you could use the batch version of our extension to automate the execution instead of using a pipeline to call the extension directly.
This guide only applies to pipelines that attempt to execute our web extensions (extensions that have a URL) using either the pipeline's Webhooks - Make Request step or HTTP - Make Request step. If you're executing our extensions by modifying a record or sending an email, you can ignore this guide.
Execute web extensions via pipelines
First, if you're using the Webhooks - Make Request step, you need to change it to the newer HTTP - Make Request step. This is vital to protect your data, since you need to select and enter a user token to use during the connection to our extension.
Next, check the domain of the extension's URL. For example, if you're using Exact Forms Plus, your URL might point to:
https://www.aws-juiced-client2.com/Juiced/ExactFormsPlus16/doc_merge_ua.aspx?
In this case, www.aws-juiced-client2.com is the domain. Keep that on hand for the next step.
Now, in the new HTTP - Make Request step, the first section asks you to create a new HTTP Account. This "account" is held on Quickbase and used to make calls to the extension, providing us authorization information. The following image shows exactly what to fill in, with an explanation for each input after the image:
HTTP Account—Select Connect new Account unless you already have an account that works for this extension and domain.
Account Name—We recommend naming this after the extension and domain. For the previous example, we'd suggest Exact Forms Plus - client2.
Authentication Type—This must be set to API Key.
Base URL—This is the domain you noted earlier. Include https:// and a trailing forward slash (/), as shown in the previous image.
HTTP Headers—You can ignore this.
API Key Name—This must be set to PipelinesToken.
API Key Value—This should be a user token that has access to all the required tables and fields that the extension needs.
Add API Key To—This must be set to Header.
After you set all of that, select the Connect button at the bottom. If successful, it removes the section and shows the account in the dropdown.
If unsuccessful, submit a technical support case so we can help.
Finally, set up the Details portion of the step. The following image shows how we suggest setting this up, with an explanation for each input after that:
HTTP Method—This should be set to GET.
Path—This should be the URL from the record that contains the extension's URL with parameters. If you have a use case where you need to hard-code the URL, keep in mind that the domain must match the prior step. For this example, the expected incoming URL from the Record Updated step is https://www.aws-juiced-client2.com/Juiced/ExactFormsPlus16/doc_merge_ua.aspx?...
HTTP Headers—You can ignore these inputs.
Query Parameters—You can ignore these inputs unless you're hard-coding the URL in Path. If you're hard-coding the URL, add any parameters for the extension here.
Expected Payload Type—Select Text (no parsing). Extensions might work with other options, but this option causes the fewest issues.
Body—You can ignore this input.
With all of that, your pipeline should now be set up to use our extension. Again, if your goal is to execute the extension automatically, we suggest you set up the batch version of the extension instead of using a pipeline to execute it directly.
If you have questions or need help changing any pipelines to be compliant with our new security measures, submit a technical support case.