Keragon's HTTP Client is a versatile feature that allows you to connect to external APIs. Whether you need to retrieve data, update records, delete entries, or create new items in an application outside Keragon's existing integrations or whenever Keragon does not support a specific action for an existing integration, the HTTP Client is your go-to solution.
Key Capabilities
- GET: Retrieve data from external services.
- POST: Create new records or submit data to external systems.
- PATCH: Make partial updates to existing records in other services.
- DELETE: Remove data from external applications.
- PUT: Completely replace or update existing records in external systems.
How to Use the HTTP Client in Keragon
- In the workflow editor, click the "+" button to add a new action.
- In the drawer that opens, search for HTTP and select it.
- From the list of the available triggering events, select the desired API operation (POST, GET, PUT, PATCH, DELETE) based on what you are trying to achieve.
- Fill out the fields of the HTTP action including the URL, Headers and Data based on the API docs of the app that you want to make this request.
- Specify the URL: Enter the endpoint of the API you’re targeting.
- Add Headers and Authentication: If the API requires headers or specific authentication (like API keys or OAuth tokens), add these in the respective sections.
- Configure Data: For POST, PUT, and PATCH requests, you’ll often need to provide a request body. Enter this in the format required by the API.
- Click the "Save" to save your configuration.
- Click the "HTTP action" in your editor
- Navigate to the 'Auth' tab in the drawer.
- Click 'Connect new account' and follow the steps to connect to the third-party app.
- In the inputs tab make sure that you have correctly set up the Authentication header
Ensure that the Authentication header matches the format expected by the third-party app exactly. Pay close attention to both the Key name and the value for the header.
For example, if an app requires authentication in the format:
"X-auth": "Bearer YOUR_TOKEN"
Then in Keragon you should:
1. Enter 'X-auth' as the key name.
2. Type 'Bearer', add a space, and then map the authentication from the 'Authentications' tab.
Example
Below is the Header configuration for Airtable in Keragon. Airtable requires the Authentication header to be in the format of:
"Authorization: Bearer YOUR_TOKEN"
Therefore, we entered 'Authorization' as the 'key name', typed 'Bearer', added a space, and then mapped the Airtable authentication from the 'Authentications' tab.
- Configure the data part based on the API requrements
Example
This is an example of using the HTTP client to make a POST request in Pipedrive for creating a new deal:
- Enter your key name in the header as required by the app for which you are making the HTTP request, and then click the 'Add' button.
- Click on the input field and select the 'Authentication' tab.
- Choose the authentication from an existing app that you have already included in the workflow.
- In the inputs tab make sure that you have correctly set up the Authentication header
Ensure that the Authentication header matches the format expected by the third-party app exactly. Pay close attention to both the Key name and the value for the header.
For example, if an app requires authentication in the format:
"X-auth": "Bearer YOUR_TOKEN"
Then in Keragon you should:
1. Enter 'X-auth' as the key name.
2. Type 'Bearer', add a space, and then map the authentication from the 'Authentications' tab.
Example
Below is the Header configuration for Airtable in Keragon. Airtable requires the Authentication header to be in the format of:
"Authorization: Bearer YOUR_TOKEN"
Therefore, we entered 'Authorization' as the 'key name', typed 'Bearer', added a space, and then mapped the Airtable authentication from the 'Authentications' tab.
- Configure the data part based on the API requrements
Example
This is an example of using the HTTP client to make a POST request in Pipedrive for creating a new deal: