Agentic Workflow Integration Actions
Audience: Administrators, Developers, Solution Architects
Purpose: Complete reference for the integration action types available in Kizen Agentic Workflows, including how to send outbound HTTP requests to external systems and use AI-powered steps for language model calls, file extraction, and audio transcription.
Overview
Integration actions connect Agentic Workflows to systems and services outside of Kizen. Use them to send data to external APIs, trigger processes in third-party platforms, and apply AI-powered processing to Records, files, and audio content. Integration actions extend the reach of an Agentic Workflow beyond the Kizen data model to the broader technology stack.
Note: For error handling, see Agentic Workflow Error Handling.
External HTTP Requests
The External HTTP Requests action sends an outbound HTTP request to an external URL.
Choose Custom HTTP Action: Select the HTTP method using the method buttons: GET, PUT, POST, PATCH, or DELETE.
Request URL: Enter the destination URL in the Request URL field. Use + INSERT MERGE FIELD to embed dynamic values, such as a Record ID, execution ID, or field value, directly in the URL.
Data Payload: For methods that support a request body (PUT, POST, PATCH, DELETE), a Data Payload field is available. Enter the payload content in the body area.
The placeholder text reads Enter Data Payload in JSON, XML, etc., indicating that any format is accepted.
Use + INSERT MERGE FIELD to insert dynamic values into the payload. The Encode Merge Fields toggle (enabled by default) automatically encodes special characters in resolved merge field values to prevent malformed payloads.
Content-Type: Use the Content-Type dropdown to set the Content-Type header for the request. The following are commonly used formats that are available:
application/javascript
application/xml
application/xhtml+xml
application/json
text/html
For other file types, reference your integrations documentation.
Customize Header (Parameters and Values): Use + ADD PARAMETER to add custom key-value pairs to the request headers.
Response and error behavior: The External HTTP Requests action is outbound only; the response payload from the external system is not returned to the Agentic Workflow and cannot be accessed in subsequent steps. As noted in the UI: anything other than 200- and 300-class responses is treated as an error.
Note: If you need to use the response data from an HTTP call in subsequent steps, use a Code Step instead. Code steps can send the request and process the response within a single step, making the response data available for downstream logic. See Agentic Workflow Code Steps.
Rate limiting behavior: When the external system returns a 429 (Too Many Requests) response, the action automatically retries.
The retry wait time is taken from the value specified in the throttle response if present; otherwise, exponential backoff is applied. The system retries up to a limited number of times before treating the step as failed.
Key Use Cases
Integration actions are applicable across any Workflow that requires data exchange with external systems or AI-powered processing within an automated process. The following examples illustrate common patterns in three industries where external integration is a core operational requirement.
Industry Examples
Insurance operations depend on real-time data exchange with underwriting platforms, claims management systems, document processors, and regulatory reporting endpoints.
Examples include:
Using External HTTP Requests to send a POST request to a claims management system when a new claim Record is created in Kizen, passing claim details in a JSON payload with merge fields
Using External HTTP Requests to send a PUT request to an underwriting platform to update a policy status when an Agentic Workflowreaches the approval stage
Using Call LLM to analyze the content of a free-text adjuster notes field and classify the claim type, writing the result to a classification field for downstream routing
Using File Extraction to extract structured data from an uploaded policy document and populate corresponding fields on the policy Record
How integration actions help:
Synchronize Kizen Records with external claims, underwriting, and policy administration systems in real time as Agentic Workflows execute
Trigger downstream processes in third-party platforms without requiring manual data re-entry or separate integration middleware
Apply AI-powered classification and extraction to unstructured data, making it available for routing, reporting, and downstream Agentic Workflow logic
Extend Agentic Workflow Workflows beyond the Kizen platform to the full technology stack used across the business
Healthcare Workflows require real-time data exchange with EHR systems, authorization platforms, patient communication tools, and regulatory reporting endpoints.
Examples include:
Using External HTTP Requests to send a POST request to an EHR system when a patient intake Agentic Workflow reaches a qualifying stage, passing patient identifiers and clinical data in a JSON payload
Using External HTTP Requests to send a GET request to an authorization platform to check the status of a prior authorization request and write the result to a field on the patient Record
Using Call LLM to summarize the content of a clinical notes field and write a structured summary to a separate field for care team review
Using Audio Transcription to transcribe a recorded patient call and store the transcript on the patient Record for documentation and compliance purposes
How integration actions help:
Keep EHR and authorization platform data synchronized with Kizen patient Records as Workflows execute
Retrieve external status data and write it back to Kizen Records without requiring manual lookup or data entry
Apply AI-powered summarization and transcription to clinical content, reducing manual documentation burden on care teams
Create auditable Records of patient interactions by storing transcripts and AI-generated summaries on the patient Record
Financial services workflows require real-time data exchange with loan origination systems, credit bureaus, compliance platforms, document processors, and client communication tools.
Examples include:
Using External HTTP Requests to send a POST request to a loan origination system when an application Agentic Workflow reaches the submission stage, passing application data in a JSON payload with merge fields
Using External HTTP Requests to send a GET request to a credit bureau API to retrieve a credit score and write the result to a field on the application Record for underwriting routing
Using Call LLM to analyze the content of a free-text application notes field and flag potential compliance issues, writing the result to a review field for compliance officer attention
Using File Extraction to extract structured data from an uploaded financial statement and populate income and liability fields on the application Record
How integration actions help:
Synchronize Kizen application and account Records with external origination, compliance, and servicing systems as workflows execute
Retrieve external data, such as credit scores and verification results, and write it directly to Kizen Records for use in downstream routing and decision logic
Apply AI-powered analysis and extraction to unstructured financial content, reducing manual review time and improving data accuracy
Extend Agentic Workflow workflows to the full financial services technology stack without requiring separate integration middleware
What's Next?
Continue to Messages Actions to learn how to send emails and text messages to Contact Records directly from an Agentic Workflow, including template selection, merge fields, and SMS character limits.
Last updated
Was this helpful?