Make a web request: Authentication

You can add authentication to any web requests to external services by adding secure credentials in Integrations.

In this article you will learn how to add and manage secure credentials in the Lumary Engagement Console.

Credentials cannot be viewed after being saved. Ensure to securely store them in a location that can be accessed later if necessary, such as a password manager.

What is a credential?

Credentials are the pieces of information, often a username and password, that are used to identify you as the authorised user of an external application.

The Lumary Engagement Console can authenticate each HTTP request made with Make a web request using secure credentials. Having a credential with the request ensures the communication between the Lumary Engagement Console and the external application is secure, and is required in some cases. Currently, the Lumary Engagement Console supports securely storing: request headers, bearer token and username and password.

• Request Headers: Similar to instructions on a parcel, request headers define the handling and processing of data in a web request. These headers provide the server with details such as data format, handling procedures, and additional context for processing the request. The Lumary Engagement Console securely records these specifications as key-value pairs, catering to a variety of operational requirements including content type, caching policies, and identification protocols.
• Bearer Token: This security token acts as a digital access card, granting entry to specific services after a successful authentication. It streamlines the validation process, allowing for a secure yet effortless way to repeatedly assert one's access rights without constant re-authentication. The Lumary Engagement Console's storage solution securely retains these tokens, automating their inclusion in requests to services that mandate verified access.
• Username and Password: These traditional identifiers serve as a fundamental method of authentication. When a system necessitates such a verification method, the Lumary Engagement Console's secure storage ensures these credentials are safely stored and accurately transmitted. This preserves the integrity and confidentiality of the user's access credentials.

Adding credentials to the Lumary Engagement Console

In the Integrations page, go to Setup new connection and select Web request credentials.

Then, you will need to select the type of credentials you wish to store.

Adding a request header

Request headers are key-value pairs that are in the header of the HTTP request.

1. Give a unique, helpful name to the credentials.
2. Add an optional description to further describe what the credentials are used for (e.g. Sales CRM authentication).
3. Enter credentials key-value format.
4. Save credentials.

Adding a bearer token

A bearer token is a string that is passed in the Authorization header of the HTTP request.

1. Give a unique, helpful name to the credentials.
2. Add an optional description to further describe this integration.
3. Enter bearer token.
4. Save credentials.

Adding a username and password

Username and password that is passed in the Authorization header of the HTTP request.

1. Give a unique, helpful name to the credentials.
2. Add an optional description to further describe this integration.
3. Enter username and password.
4. Save credentials.

Adding saved credentials to web requests

After securely storing your credentials in the Lumary Engagement Console, you can easily select them within the Make a Web Request node. This node allows you to execute HTTP requests as part of your automated workflows. By selecting saved credentials during the node configuration, the Lumary Engagement Console ensures that each web request it makes on your behalf is authenticated, thus maintaining the security and integrity of data exchanges with external services.

For a detailed guide on configuring the make a web request node, see Make a web request Date Action

Updating credentials

1. Navigate to Integrations > My integrations
2. Under Action connections, select on the settings icons of the credential you want to update.
3. Update fields, Name and Description, as necessary.
4. Click on Update connection.

You cannot read credentials before updating them as they are stored securely and cannot be surfaced.