Use Automate to turn supported file uploads into recurring cloud-storage ingestion workflows. Yarken uses the selected connection, folder, Data Mapping Template, and schedule to create and run the related pipeline.
Automate focuses on file ingestion only. Any additional processing or transformation must be configured in upload rules.
Go to Admin > Pipelines > Automate to review file types that support automation and start a new setup.
What you can do
Use Automate to:
-
Automate recurring uploads for supported file-based data types.
-
Retrieve files from a selected folder in Azure Blob Storage, AWS S3, or Google Cloud Storage.
-
Reuse or create a Data Mapping Template for recurring uploads.
-
Schedule ingestion to run hourly, daily, or monthly.
-
Start automation from the central Automate page or from a previously uploaded file.
-
Review whether automation is active for each supported file type.
-
Replace existing expense data for a target month before importing a new Expenses file, where required.
-
Manage the generated pipeline from the Pipelines page.
-
Delete before load is available only for Expenses (spend) file uploads. Use it when the recurring file should replace existing expense data for the target month.
Before you begin
-
Configure a BASIC cloud storage connection for the source location.
-
Confirm that the source folder contains only the files you want Yarken to process.
-
Prepare or identify the correct Data Mapping Template.
-
Keep the source file structure and column headers consistent across recurring uploads.
-
Confirm the schedule you want to use.
Automate processes files from the folder you select. Keep unrelated, test, draft, or incomplete files out of that folder.
How Automate works
A typical Automate workflow follows this sequence:
-
Select a supported file type.
-
Select the cloud storage provider and connection.
-
Select the source folder or directory.
-
Review or create the Data Mapping Template.
-
Set the upload schedule.
-
Review the generated pipeline name and save the setup.
-
Yarken uses the linked pipeline to process matching files on the configured schedule.
|
Component |
Role in Automate |
|---|---|
|
Connection |
Provides access to the selected cloud storage location. |
|
Folder or directory |
Defines where Yarken looks for files to process. |
|
Data Mapping Template |
Maps source file columns to the Yarken destination fields. |
|
Schedule |
Controls how often the linked pipeline checks for and processes files. |
|
Pipeline |
Runs the recurring ingestion workflow created through Automate. |
Automate does not configure Advanced Integrations. For Yarken-managed provider workflows, see Advanced integrations.
Supported file types
The Automate page lists the file types that support recurring file ingestion in your environment.
Understand the Automate status
The Automate icon shows whether recurring ingestion is configured for a file type:
-
Blue Automate icon — Automation is active.
-
Gray Automate icon — Automation is inactive or has not been configured.
You cannot deactivate automation directly from the Automate page. Manage the linked pipeline from Admin > Pipelines > Pipelines.
Choose where to start
You can start Automate from two locations.
|
Entry point |
Use it when |
Mapping behavior |
|---|---|---|
|
Admin > Pipelines > Automate |
You want to browse supported file types and configure recurring ingestion from one place. |
Select an existing template, create one, or replace the current template where supported. |
|
UPLOADED FILES |
You already uploaded a file manually and want to automate future files with the same structure. |
Yarken uses the mapping from the selected uploaded file as the starting mapping. |
Set up automation from the Automate page
Step 1: Open Automate
-
Go to Admin > Pipelines > Automate.
-
Find the file type you want to automate.
-
Select the gray Automate icon.
Automate icon
Step 2: Select the cloud storage provider
Select the storage provider that contains the recurring source files.
-
Azure Blob Storage
-
AWS S3
-
Google Cloud Storage
If the required connection does not exist, create it before you continue.
See Connections.
Step 3: Select the connection
Select the BASIC cloud storage connection that provides access to the source location.
Test updated credentials from the Connections page before you rely on the connection for scheduled ingestion.
Step 4: Select the folder or directory
Enter or select the source folder that contains the files Yarken should process.
Yarken processes only files from the configured folder.
Yarken may use the data template file name as the default directory name. Change the path when your cloud storage uses a different folder structure.
Step 5: Review the Data Mapping Template
Review the template that Yarken will apply to recurring files.
-
If a suitable template exists, keep or select it.
-
If the file structure requires a different mapping, create or replace the template where supported.
-
If you started from UPLOADED FILES, Yarken uses that file's mapping as the starting mapping.
Review the mapping whenever the source file structure changes. Incorrect or missing mappings can cause the pipeline to fail or load incomplete data.
Step 6: Choose whether to delete existing Expenses data
For Expenses (spend) file uploads, you can use Delete before load when you need to replace the existing records for the target month.
When selected, Yarken removes the existing expense records for that month before importing the new file.
Delete before load removes existing data. Confirm the target month and source file before you continue. This option is available only for Expenses (spend) uploads.
Step 7: Set the upload schedule
Choose how often Yarken should run the recurring ingestion:
-
Hourly
-
Daily
-
Monthly
Step 8: Review and save the automation
Yarken generates a pipeline name based on the selected file type. Update the name if required.
-
Review the connection, folder, mapping, and schedule.
-
Select SAVE.
-
Confirm that the Automate icon turns blue for the file type.
The recurring ingestion is configured. Manage the generated pipeline from Admin > Pipelines > Pipelines.
Set up automation from UPLOADED FILES
Use this workflow when you already loaded a file manually and want future files to use the same mapping structure.
Step 1: Open the uploaded file
-
Open the applicable area in Yarken Designer.
-
Select the UPLOADED FILES tab.
-
Find the file you want to automate.
-
Select the Automate icon in the Actions column.
Automation from UPLOADED FILES
Step 2: Review the inherited mapping
Yarken uses the field mapping from the selected uploaded file as the starting mapping for future automated uploads.
Review the mapping before you save the automation. Replace or create a template when the recurring file structure requires a different mapping.
Step 3: Complete the automation setup
Select the connection, folder, schedule, and remaining pipeline details. Then save the automation.
Deleting the original uploaded file later does not stop the recurring automation. The linked pipeline continues to control the scheduled ingestion.
Manage an automated upload
After you save an Automate setup, manage the linked workflow from the Pipelines page.
Edit the automation
Edit the linked pipeline when you need to change:
-
The source connection.
-
The source folder or directory.
-
The Data Mapping Template.
-
The schedule.
-
The pipeline name or description.
Deactivate the automation
-
Go to Admin > Pipelines > Pipelines.
-
Find the linked BASIC pipeline.
-
Deactivate the pipeline.
The Automate icon becomes gray when the linked automation is no longer active.
Delete the automation
Delete the linked pipeline when you no longer need the recurring workflow.
A Data Mapping Template referenced by an active or inactive pipeline cannot be deleted. Update or remove the linked pipeline before you delete the template.
For full pipeline management instructions, see Manage BASIC pipelines.
Recommended folder and file practices
After automation runs
After the linked pipeline completes successfully:
-
Review the pipeline run status.
-
Confirm that Yarken processed the expected files.
-
Open the Yarken feature associated with the destination data type.
-
Select the applicable entity, year, and month.
-
Verify that the expected records are available.
-
Refresh the affected cube when you need immediate reporting results.
-
Review the data in the relevant report, dashboard, or Analytics data area.
For refresh guidance, see Cube refresh and best practices for Pipelines.
Troubleshoot Automate
|
Issue |
What to check |
|---|---|
|
The Automate icon is gray |
Confirm that automation has been configured and that the linked pipeline is active. |
|
The source folder is not available |
Verify the connection, storage permissions, and folder path. |
|
The pipeline does not process a file |
Confirm that the file is in the configured folder and that its structure matches the selected Data Mapping Template. |
|
The wrong fields are loaded |
Review the selected template and compare its source mappings with the current file headers. |
|
The source file structure changed |
Update the supported Data Mapping Template before the next scheduled run. |
|
Automation stopped after a credential change |
Test the BASIC connection and confirm that the storage credentials and permissions are still valid. |
|
A run succeeds, but the new data is not visible in reporting |
Verify the destination data first, then refresh the affected cube if you need immediate reporting results. |
|
You cannot delete the Data Mapping Template |
Check whether an active or inactive pipeline references the template. Update or remove the pipeline first. |
For additional help, see Monitor pipeline runs.
Related content