⏩ Content Summary:
Learn how to set up integrations with the software of your choice and automate the sending of HTTP requests through Pipefy to achieve a more agile, integrated, and streamlined operation.
Creating multiple integrations between Pipefy, and the software you want is possible by using solutions like Zapier and Workato, or by setting up integrations through an API.
You can also set up integrations using HTTP requests (the client-server protocol for sending and retrieving data widely used on the internet), and thus create specific automations that send requests to the systems and tools you need.
By using this method, you’ll establish more robust and flexible integrations with Pipefy, as well as automate them.
How to create automations to send HTTP requests
To create automations involving HTTP requests, click on the Automate button, located in the upper right corner of the screen. Then, just click Create automation.
On the left side, you can choose any of the events (except for recurring automation), such as when a card is created, when a field is updated, or when an alert is triggered, and fill in the options that meet your requirements.
After choosing the triggering event, it's time to choose the action. Click the Make an HTTP request button to configure the specifics of the automation.
Here, we find the following options:
Method: Post, Put, Delete, GET, or Patch; choose the method of your HTTP request.
URL: Enter the service address to which the HTTP request must be sent. Here, it is possible to insert card fields to compose the address. For example: https://api-url.com/endpoint.
Authentication: At this point, you must enter the authentication information for the HTTP request. Attention: the automation does not accept OAuth authentication at this time.
No Auth: for cases where the request does not require authentication.
Authorization: for cases in which authentication happens through the HTTP. Header Authorization.
API Key: for cases in which you want to inform not only the authentication token, but also the key in which it should be inserted.
In this case, you must select whether the authentication will be sent in the Headers or through the URL (Query Params).
Header/Value: Here, we have the headers in JSON format to be sent with the HTTP request. It is not necessary to pass the Content-Type Header: application/JSON.
Request content type: Where only JSON content is accepted for now.
Request body: Fill in the content to be sent in the HTTP request in JSON format.You can insert card fields to compose the body here. Example:
Response: Select a long text field in your pipe where the request response will be inserted when the automation runs. The field is not mandatory; you don't need to select any field if you do not want to receive the request response. For now, the purpose of this field is for feedback on the automation results. As the entire response is entered into the field, it is not yet possible to use parts of it to compose your process.
JSON schema: This last option is essential to search and use information from the HTTP responses in your Pipefy processes.
To do this, fill this field with an example of the expected response to this request. This information will be available when you create a new automation with the event An HTTP response is received.
For example, if you are making an HTTP call to retrieve data for an address based on the ZIP code, you can expect a response like the following:
You can use an example like this in the JSON schema field of your automation.
After creating the configuration, just click on Create automation and save it. That's it! From now on, you will have a dedicated automation for integrations through HTTP requests.
From the moment you create your first automation with the action of making HTTP calls, you can also use the An HTTP response is received event to further enrich the information in your process.
There are several applications of HTTP requests, including use cases for the processes of multiple departments. Here are examples from different teams:
HTTP requests in Human Resources
Integration with password manager software to request the addition or removal of employees to access the company's systems and tools
Integration with ASO software (occupational health certificate) to collect the results of admission and dismissal exams
Integration with background check software to automatically collect and populate candidate information on cards
Integration with DocuSign/D4sign and other document submission software to collect digital signatures
Integration with messaging applications and software, such as Microsoft Teams and Slack, to facilitate and streamline employee communication
Integration with eSocial to automatically send data to the platform
Integration with the spreadsheet and ERP system to add or change information, in addition to synchronizing it (cost center, areas, positions, employees, etc.)
Integration with time attendance software to collect records, absences, and justifications, among other options
HTTP Requests in Purchasing
Data extraction by OCR
Integration with punchout listings
Integration with messaging apps (like Slack) to make approval requests
Integration with software to open purchase requests
Integration with ERP bases to synchronize data (suppliers, purchase orders, accounts payable, etc.)
Integration with third-party apps for sourcing vendors, background checks, and more
HTTP Requests in IT
Automatically add or remove users from groups
Consolidation and addition of information in DBs, among other options
Automatically add or remove records in legacy systems such as ERPs, HCMs, CRMs, and Payroll