Manage Automation Recipes in Yarken

Overview

Automation recipes define the workflows that automate data movement and actions between Yarken and external applications.

A recipe consists of a trigger that starts the workflow and one or more actions that are performed when the trigger is activated. Depending on the integration, recipes can retrieve data, upload files, synchronize records, trigger Yarken pipelines, or update external systems.

Recipes are managed directly within Yarken using the embedded automation interface.

Open the Automation Recipes page

To view available automation recipes:

1. Sign in to Yarken.

2. Navigate to Admin > Pipelines.

3. Select the ADVANCED tab.

The ADVANCED tab displays the automation recipes available for your environment.

Review a recipe

Before activating a recipe, review its configuration to ensure it meets your business requirements.

Depending on the recipe, review:

• The configured trigger.

• The connected applications.

• The execution schedule.

• The required connections.

• Any configurable settings or input values.

If changes are required, update the recipe before enabling it.

Start a recipe

Start a recipe after all required connections have been authorized and tested.

To start a recipe:

1. Open the recipe.

2. Review the configuration.

3. Select Start.

   

4. Confirm that the recipe status changes to Running.

Once started, the recipe runs according to its configured trigger.

Stop a recipe

You can stop a recipe at any time.

Stopping a recipe prevents it from processing new events or scheduled runs until it is started again.

To stop a recipe:

1. Open the recipe.

2. Select Stop.

3. Confirm the action.

Use this option when performing maintenance, updating configuration settings, or troubleshooting an issue.

Recipe triggers

A trigger determines when a recipe starts.

Depending on the integration, recipes may use one of the following trigger types.

The trigger type is predefined by the recipe and may vary depending on the integration.

Test a recipe

Before enabling a recipe in production, perform a test run whenever possible.

Testing confirms that:

• The required connections are available.

• Authentication succeeds.

• The workflow completes successfully.

• Data is processed correctly.

• No runtime errors occur.

Resolve any issues before enabling the recipe for regular use.

Monitor recipe execution

After a recipe has been activated, monitor its execution to ensure that it continues to run successfully.

Review the following information regularly:

• Current status

• Last execution time

• Execution history

• Failed jobs

• Error messages

• Processing duration

Monitoring helps identify issues before they affect downstream reporting or automated processes.

Recipe status

Each recipe displays its current execution status.

Best practices

Follow these recommendations when managing automation recipes:

• Verify that all required connections are authorized before starting a recipe.

• Test new or updated recipes before enabling them in production.

• Monitor execution history regularly.

• Review failed jobs promptly.

• Stop recipes before making significant configuration changes.

• Disable recipes that are no longer required.

Troubleshooting

Related content

Continue with the following guides:

• Configure AWS Trusted Advisor Integration

• Automate File Uploads from Cloud Storage

• Troubleshoot Advanced Integrations