Titan Support

How can we help you?

Platform

Support center Flow Flow Integrations API Hub Configuring an API

Configuring an API

Business Background

APIs connect Titan with the external systems your business relies on. This guide explains how to configure an API call in the API Hub using Titan Flow.

Titan Solution

Titan Flow allows you to build, test, and automate API requests directly in your project. URL setup, authentication, parameters, and data mapping all occur within the Flow Builder, allowing you to integrate any REST API in minutes.

Best Practices

Test your API calls with sample data before deploying them to production.
Remove tokens or credentials before exporting configuration files.
Keep responses lightweight and structured for efficient mapping.
Use sample data during initial testing.
Remove credentials before exporting configuration files.
Enable logging for debugging complex calls.
Keep payloads concise to improve performance.

How to Guide

Step 1 – Add the API Hub Node

Open an existing project in Titan Flow, or create a new one.
Click the + icon to add a new node.
Select Integrations > API Hub, then click Next.

The Custom API Hub screen opens.

Edit the node name if needed.
Add your REST API URL (required). Optionally, set the Field to use a variable.
Select the HTTP method for your API call

Method	Description
GET	Retrieve data from a server.
POST	Create new resources on the server.
PUT	Fully update an existing resource.
PATCH	Partially update a resource.
DELETE	Remove a resource.
HEAD	Return headers only.
OPTIONS	Check available methods.

Step 2 – Import or Export a Request

The API Hub enables you to import or export configurations, saving time, reducing duplicate work, and allowing you to reuse setups across projects.

Import from Postman

You can import an existing API request from Postman to set up complex configurations that have already been tested quickly.

In the API Hub, click Import.
Choose a Postman collection (.json) file.
Only the first request in the Postman collection will be imported. To ensure the correct one is used, either make it the only request in the collection or move it to the top position before exporting.
Browse to the .json file and click Open.

When to use Postman Import

To set up complex API requests that already exist and have been tested in Postman.
To avoid manual reconfiguration of headers, parameters, and bodies.
To speed up the process of connecting to third-party APIs.

Import from another Titan Project

You can also reuse existing API Hub configurations you created in another Titan project.

From Project A, export the API Hub node as a .json file.
In Project B, open the API Hub and click Import.
Select the exported .json file.
The full configuration will be automatically populated, including headers, body, and authentication.

Export a Request

Export a configured API Hub node to reuse or share it with your team.

Click Export in the API Hub node.
Choose a folder and click Save.

Important Notes

If Authorization is Basic or Bearer Token, credentials will be included. Clear them before exporting if you don’t want sensitive data shared.

This is useful for standardizing integrations or replicating setups in staging and production environments.

Warning:

If your Authorization type is Basic or Bearer Token, credentials will be exported. Remove sensitive data before exporting.

Step 3 – Configure Parameters

Parameters define dynamic values in your API request URL.

Open the Parameters tab.
Click Add Parameter.

Key

Enter a key manually. This defines the parameter name used in the request.

Value

Choose how to set the value for that key:

Static – Enter a fixed value manually.
Field – Use a variable or Record ID.

API Hub screen - Headers — API Hub screen – Headers

Step 4 – Configure Authorization

Use this tab to set up authentication for your request.

Available Authorization Types

No Auth
Basic Auth – Enter username and password.
Bearer Token – Enter the token string.
OAuth 2.0 – Choose one of three grant types.

API Hub screen - Body — API Hub screen – Body

OAuth 2.0 Notes

Depending on the Grant Type you select, a Generate Token button may appear.
The Generate Token option is only available when using the Authorization Code grant type.
Before you can generate a token, you must first save the configuration. Once saved, you can return to the main OAuth 2.0 modal to generate the token.
If you don’t see the Generate Token button immediately, confirm that:
- You have selected the Authorization Code or Authorization Code (PKCE) grant type.
- The configuration has been saved successfully.

Note: The Client Credentials grant type does not support token generation.

This behavior is intentional and prevents token generation errors before setup is complete.

Grant Type	Requires User Login	Uses Client Secret	Best For
Authorization Code	Yes	Yes	Web apps with backend
Authorization Code (PKCE)	Yes	No	Mobile or browser apps
Client Credentials	No	Yes	Server-to-server apps

Each grant type has its own configuration flow in Titan.

Refer to the sections below for details.

Authorization Code Flow

Requires Client ID, Client Secret, and registered Callback URL.
Titan redirects the user to your API’s Auth URL, retrieves an authorization code, and exchanges it for an access token using the Token URL.
Best for backend-secured web apps.

Authorization Code (PKCE) Flow

Adds a code challenge and code verifier for enhanced security.
Does not require a client secret, making it ideal for browser or mobile apps.

Client Credentials Flow

No user interaction required.
Uses only Client ID and Client Secret.
Best for background or system-level integrations.

Step 5 – Add Headers

Open the Headers tab.
Click Add Header.

Enter a Key

Enter a key manually. This defines the parameter name used in the request.

Value

Choose how to set the value for that key:

Static – Enter a fixed value manually.
Field – Use a variable or Record ID.

Common headers:

Content-Type
Authorization
Custom headers required by the API

Step 6 – Configure Body

If your request method is POST, PUT, or PATCH, add data under the Body tab.

Select the content type:

None
form-data – Key/value pairs that can include files.

x-www-form-urlencoded – Key/value pairs encoded as a single query string.

JSON – Enter raw JSON data.

Binary – Upload raw binary files.

You can insert Titan variables into JSON or form data using the + icon.

Step 7 – Define Output

Use this tab to decide how Titan handles the data returned from your API request. Unlike Postman, which only displays the response, Titan allows you to map and store the output for reuse in other parts of your project.

Open the Output tab.
Choose the output format:
- String – Store the entire response as plain text. Depending on how you plan to use the data, you can still use this even if the response is JSON.
- JSON – Use when extracting or mapping specific fields from a structured response.

API Hub screen - Output — API Hub screen – Output

Plain Result

Declare a Plain Result variable. This variable stores the entire API response, regardless of format.

When using JSON, the variable will store the Plain Result, which contains the complete response data. This response is often in JSON format but can include any data returned by the request.
You can later reference this variable in Flows, emails, or other parts of your project.
Declaring it ensures the entire response is available for debugging or mapping later.

Mapping Path

Use Mapping Path to extract specific values from the response and assign them to variables.

Example: If the API response is { “data”: { “account”: { “name”: “Alex”, “email”: “[email protected]” }}}, you can:
- Store the full response in the Plain Result variable.
- Set the Mapping Path to data.account.name and assign it to a variable (for example, accountName).
- Set another Mapping Path to data.account.email and assign it to a variable (for example, accountEmail).
Each Mapping Path extracts one value from the full response.
The mapped variables can then be used anywhere in your Titan project, for example, to display data in a web project field, send an email, or update another process.

Example:

API response:

{

“data”: {

“account”: {

“id”: “0015g00000XyzAbC”,

“name”: “Alex”,

“email”: “[email protected]”

}

Plain Result: Stores the complete response above.
Mapping Paths:
- data.account.id → variable accountId
- data.account.name → variable accountName
- data.account.email → variable accountEmail

You can then use these variables anywhere in your Titan project, such as sending them in an email, updating a record, or displaying them on a screen.

Step 8 – Handle Success and Error Responses

After configuring your API output, you can define how Titan should respond when the API request succeeds or fails.

In the Builder, the Custom API Hub Call element includes two paths:

After Finish – Triggered when the request is successful.
On Cancel – Triggered when the request fails or is canceled.

You can use these nodes to create different paths in your flow. For example, to display data in a web project field, send an email, or update another process.

Screenshot showing the After Finish and on Cancel paths — Custom API – After Finish and On Cancel paths

Note:

Part of this workflow:

The Only Forms Solution Built 100% in Salesforce.

Slack an expert

Document Studio

Experience Studio

Go Unlimited

By Industry