Use Advanced Integrations to connect Yarken with supported external systems through integrations that Yarken deploys and maintains for your environment.
Advanced Integrations are not enabled by default. Yarken enables the required integrations for your environment during implementation or onboarding. The integrations available to you can vary by environment.
What Advanced Integrations do
Advanced Integrations automate supported data collection and ingestion workflows that require provider-specific credentials, permissions, or managed integration logic.
Depending on the integration, you can use Advanced Integrations to:
-
Collect AI usage, cost, token, and metrics data.
-
Import provider recommendations.
-
Automate file ingestion from supported cloud storage providers.
-
Load provider data into the applicable Yarken destination for reporting and analysis.
What you manage
After Yarken deploys the integration, your organization manages the customer-facing connection and pipeline controls.
|
Activity |
Responsibility |
|---|---|
|
Enable and deploy the Advanced Integration |
Yarken |
|
Maintain the underlying integration and transformation logic |
Yarken |
|
Prepare provider credentials, roles, and permissions |
Your organization |
|
Authorize Advanced Connections |
Your Yarken administrator |
|
Run, activate, or deactivate Advanced pipelines |
Admin or Cost Model Manager |
|
Review pipeline status and run history |
Admin or Cost Model Manager |
|
Validate imported data |
Your organization |
You cannot edit the deployed Advanced Integration logic in Yarken. Yarken manages the underlying integration workflow. You manage the supported connection and pipeline controls exposed in the Yarken interface.
Where to manage Advanced Integrations
Advanced Integrations use two customer-facing areas in Yarken:
|
Area |
Location |
Use it to |
|---|---|---|
|
Advanced Connections |
Admin > Pipelines > Connections > ADVANCED |
Authorize the provider connection and review whether it is Access requested or Connected. |
|
Advanced pipelines |
Admin > Pipelines > Pipelines > ADVANCED |
Run the integration, activate or deactivate recurring execution, and review run status and history. |
How Advanced Integrations work
Advanced Integrations use several components to securely retrieve, process, and load data from supported external systems into Yarken. The components used depend on the integration.
|
Component |
Purpose |
|---|---|
|
Advanced Connection |
Securely authenticates Yarken with the external provider using the required credentials and permissions. |
|
Yarken-managed integration workflow |
Retrieves data from the source and performs the processing required by the integration. |
|
Data Mapping Template — where required |
Maps source data to the applicable Yarken structure before ingestion. For Advanced Integrations, Yarken applies and manages the required template. You do not need to configure or edit it. |
|
Advanced pipeline |
Runs the deployed integration and provides customer-facing controls for manual runs, activation, status, and run history. |
|
Yarken destination |
Stores the processed data in the applicable Yarken area, such as AI Usage Data, Cloud Usage Data, Companion Metrics, or Recommendations. |
Typical integration flow
-
External provider
The external system provides the source data, such as AI usage, cloud files, metrics, or recommendations.
-
Advanced Connection
Yarken uses the authorized connection to securely access the provider using the credentials and permissions supplied by your organization.
-
Yarken-managed integration workflow
The deployed integration retrieves and processes the source data. Yarken manages the underlying workflow and transformation logic.
-
Data Mapping Template — where required
For integrations that require data mapping, Yarken automatically applies the required Data Mapping Template. You do not configure or edit this template.
-
Advanced pipeline
The pipeline runs the integration and lets authorized users run it manually, activate or deactivate recurring execution, and review run results.
-
Yarken destination
Yarken loads the processed data into the destination configured for the integration. Depending on the integration, this can include AI Usage Data, Cloud Usage Data, Companion Metrics, Recommendations, or another supported Yarken destination.
Note: Not every Advanced Integration uses every component. The exact workflow depends on the provider and the type of data being ingested.
About the integration technology
Yarken Advanced Integrations are powered by Workato, which provides the embedded integration technology used to connect supported external systems with Yarken. You continue to authorize connections, run integrations, and monitor activity from within Yarken.
BASIC and ADVANCED integrations
|
Integration type |
Use it when |
Setup ownership |
|---|---|---|
|
BASIC |
You are configuring a supported native Yarken connection and pipeline for standard cloud storage or API ingestion. |
Your administrator or Cost Model Manager creates and manages the supported connection and pipeline in Yarken. |
|
ADVANCED |
You are using a supported integration that requires a Yarken-deployed workflow, provider-specific authorization, or managed transformation logic. |
Yarken deploys and maintains the integration. Your organization authorizes the connection and operates the exposed pipeline controls. |
Supported Advanced Integrations
The integrations available to your organization depend on what Yarken has enabled for your environment.
|
Category |
Supported integration |
Purpose |
|---|---|---|
|
AI usage and consumption |
Collect Claude Enterprise cost and usage data for AI Consumption reporting. |
|
|
Collect OpenAI API Platform usage and cost data for AI Consumption reporting. |
||
|
Collect GitHub Copilot usage and related reporting data. |
||
|
Collect supported Cursor AI usage data. |
||
|
Collect supported AI usage data from a configured LiteLLM deployment. |
||
|
Collect supported Azure AI Foundry metrics into Companion Metrics for reporting and analysis. |
||
|
Cloud storage |
Automate file ingestion from supported Amazon S3 storage. |
|
|
Automate file ingestion from supported Azure Blob Storage. |
||
|
Automate file ingestion from supported Google Cloud Storage. |
||
|
Recommendations |
Import supported AWS optimization recommendations into Yarken. |
Only integrations enabled for your Yarken environment appear in the ADVANCED tabs. If you need an integration that is not available, contact your Yarken implementation or support contact.
Before you begin
Before you authorize or run an Advanced Integration:
-
Confirm that Yarken has enabled the required integration for your environment.
-
Review the provider-specific prerequisites for the integration.
-
Prepare the required provider credentials, roles, permissions, or service accounts.
-
Use a Yarken administrator account to authorize the Advanced Connection.
-
Store provider secrets according to your organization's credential-management policy.
Where to go next
|
Task |
Go to |
|---|---|
|
Authorize a provider connection |
|
|
Run, activate, deactivate, or review an Advanced pipeline |
|
|
Configure automated cloud-storage ingestion |
|
|
Configure Azure AI Foundry metrics |
|
|
Configure AWS recommendation ingestion |
|
|
Resolve an Advanced Integration issue |
|
|
Configure Anthropic AI Consumption integration |
|
|
Configure OpenAI AI Consumption |
|
|
Configure GitHub Copilot usage integration |
|
|
Configure Cursor AI usage integration |
|
|
Configure LiteLLM AI usage integration |
Related content