What is the Enviar HTTP Request action?
Enviar HTTP Request is a Workflow template action that allows Buk to automatically communicate with external systems (for example, other software or internal platforms) whenever a request from that template is triggered, which can be done manually or automatically depending on how you configure it.
Simply: when an automation or a request is executed (for example, a hire, termination or job movement), Buk can send basic information about the employee and the company to another system to notify that the change occurred.
This allows, for example, updating internal systems, synchronizing people data, triggering processes in IT or HR tools, recording events in external systems or keeping different platforms integrated, without anyone having to do it manually.
This action is designed for technical integrations. Its configuration must be carried out together with the IT team or the expert area of your organization, responsible for the external system and its security.
Buk does not configure or validate external systems, since these depend on each company's infrastructure, rules and definitions.
This action is available only in templates of typeFlexible, both in automations and in manual templates.
What do you need beforehand?
Have Workflow and API enabled (Exclusive with the Plataforma Pro plan)
Have the permissionWorkflow > Plantillas y Solicitudes en Modificación
Have permission forAPI> Accesos API > Webhooksset to Yes
Have the external endpoint to which you want to send the information and know which method, authentication and format it requires.
How to configure the Enviar HTTP Request action?
Within the final stage of your flexible template:
1. Select the action
Click onAñadir acciónand chooseEnviar Request HTTP.
A modal will appear with the fields necessary to configure the request.
2. Configure the method and the URL
HTTP Method:select the method that your external system needs:
GET
POST
PUT
PATCH
DELETE
URL:Enter the address of the external endpoint to which we will send the request. Example format: https://tudominio.cl
This request will be sent automatically every time the automation event is triggered.
3. Define the authentication type (optional depending on your API)
On theAuth, choose how your request will be authenticated:
No authentication
Basic Auth(username + password)
Bearer Token
API Key(included in the header or in URL parameters, depending on what your external API requires)
Fill in the fields according to what the external service requests.
4. Build the Body (message content)
On theBodyyou can define the content that Buk will send in the request.
Tenant URL
Date
Event type
Employment status
Employee ID
Full name
Corporate email
RUT / DNI / RFC / CPF according to country
Company name
Area ID
Position
Workflow ID
These values will be populated automatically based on the employee and the request that triggered the automation.
For now, it is not possible to write free text or add custom fields: the set of fields is defined.
Body JSON:
Los campos disponibles en el Body son:
- **tenant_url**: URL del tenant
- **date**: Fecha
- **event_type**: Tipo de evento
- **employment_status**: Estado de empleo
- **employee** (datos del colaborador):
- **employee_id**: ID del colaborador
- **full_name**: Nombre completo
- **email_corporate**: Email corporativo
- **rut** (u otro identificador según país)
- **organization** (datos de la organización):
- **company_name**: Nombre de la empresa
- **area_id**: ID del área
- **job_role**: Cargo
- **metadata**:
- **workflow_id**: ID del workflow
Un ejemplo de body JSON es:
```json
{
"tenant_url": "chile",
"date": "2025-12-11T13:28:51-03:00",
"event_type": "workflow_action",
"employment_status": "activo",
"employee": {
"employee_id": 2758,
"full_name": "Rodrigo Contreras",
"email_corporate": "rodrigo@correo.cl",
"rut": "20.202.020-2"
},
"organization": {
"company_name": "LRE MEDIPASS-INTEGRAMDEDICA",
"area_id": 200,
"job_role": "Product Owner"
},
"metadata": {
"workflow_id": 2292
}
}
What happens when the automation runs?
Each time the configured event occurs, Buk will automatically send the request with:
The selected method
The defined URL
The chosen authentication
The body values populated with the employee, the organization and the workflow information
If the request fails (for example, because an endpoint is down or due to an authentication error), the flexible request will show the statusErrorin its execution, indicating that the external action could not be completed.
Best practices
Verify that the external API accepts the selected method.
Ensure your external API can work with the data format Buk sends
Test your endpoint with external tools before configuring it in Buk.
Keep your tokens or credentials up to date to avoid authentication errors.
🤖 This article was translated using artificial intelligence. View original article.