What Apify Does in Workflows
Apify connects external scraping and data collection jobs to Kyrios Workflows.
Apify triggers start a Kyrios workflow after an Apify run finishes.
Apify actions let Kyrios send work to Apify or retrieve Apify results during a workflow.
Prerequisites
Before using Apify in Workflows, confirm that:
You have access to Automation → Workflows
You have an Apify account
You have permission to connect integrations
Premium workflow usage may apply
Connect Apify from Settings
Use this method when you want to connect Apify before building a workflow.
Go to Settings
Select Integrations
Find Apify
Click Connect
Authorize the Apify connection
Open a Workflow
Use this path to open the workflow where Apify will be used.
Go to Automation
Select Workflows
Open an existing workflow or create a new workflow
Connect Apify from a Workflow Step
If Apify is not already connected, Kyrios displays Connect now when you select an Apify trigger or action.
Add an Apify trigger or action
Click Connect now
Authorize Apify
Return to the workflow step
Continue configuring the trigger or action
Available Apify Triggers
Apify triggers start a workflow after activity finishes in Apify.
Trigger | What It Does |
Finished Actor Run | Starts the workflow when an Apify actor run finishes |
Finished Task Run | Starts the workflow when an Apify task run finishes |
Add an Apify Trigger
Use an Apify trigger when Kyrios should wait for Apify activity to finish before the workflow starts.
Click Add New Trigger
Search for Apify
Select Apify
Choose Finished Actor Run or Finished Task Run
Configure the required Apify fields
Save the trigger
Test an Apify Trigger
Testing confirms that Kyrios can receive Apify trigger data.
Configure the Apify trigger
Click Find New Records
Wait for Kyrios to fetch the sample data
Review the trigger data response
Click Save Trigger
Use the returned data for mapping values into later workflow steps.
Available Apify Actions
Apify actions let Kyrios send requests to Apify or retrieve Apify results.
Action | What It Does |
Run A Task | Runs a predefined Apify task |
Run An Actor | Starts an Apify actor |
Scrape Single URL | Extracts data from one webpage |
Fetch Dataset Items | Retrieves dataset results from Apify |
Find Last Task Run | Finds the most recent task run |
Find Last Actor Run | Finds the most recent actor run |
Fetch Key-Value Store Record | Retrieves a record from Apify key-value storage |
Set Key-Value Store Record | Saves a record to Apify key-value storage |
Add an Apify Action
Use an Apify action when a Kyrios workflow should send work to Apify or retrieve Apify data.
Click the + icon where the action should run
Search for Apify
Select the Apify action
Configure the required fields
Save the action
Use a Wait Step Before Fetching Results
Use a Wait step when a workflow starts an Apify actor or task and later needs the result.
This gives Apify time to finish before Kyrios runs actions such as:
Fetch Dataset Items
Find Last Task Run
Find Last Actor Run
Without a Wait step, the workflow may try to fetch results before Apify finishes processing.
Use Case: Local Business Lead Generation
Goal: Add scraped business leads into Kyrios and start outreach.
Workflow structure:
Trigger: Finished Actor Run
Action: Fetch Dataset Items
Action: Create Contact
Action: Send Email
Example:
An Apify actor collects local business leads. When the actor run finishes, Kyrios fetches the dataset, creates contacts, and sends an outreach email.
Use Case: Competitor Monitoring and Team Alerts
Goal: Notify the team when Apify returns monitored website data.
Workflow structure:
Trigger: Finished Actor Run
Action: Fetch Dataset Items
Action: Internal Notification
Example:
An Apify actor monitors a competitor website. When the run finishes, Kyrios fetches the dataset and sends an internal notification to the team.
Common Issues and Fixes
Apify does not appear in the workflow builder
Connect Apify from Settings → Integrations, then reload the workflow builder and search again.
Kyrios asks me to connect Apify inside the workflow
Click Connect now in the Apify step and authorize the integration before saving the trigger or action.
No data is returned from Apify
Confirm that the Apify run completed successfully.
Add a Wait step before fetching returned data, then test again with a small sample.
Trigger data is not available for mapping
Run the trigger test again and confirm Kyrios fetched a successful trigger data response.
The Apify action fails
Check Execution Logs for the failed step. Common causes include missing authorization, incorrect Apify configuration, or trying to fetch results before a run finishes.
FAQ
What is the difference between Apify triggers and Apify actions?
Apify triggers start a Kyrios workflow when an Apify actor or task finishes. Apify actions run inside a Kyrios workflow to start Apify work or retrieve Apify data.
Where do I connect Apify?
You can connect Apify from Settings → Integrations or from an Apify trigger or action inside the workflow builder.
Should I use Finished Actor Run or Finished Task Run?
Use Finished Actor Run when the workflow should start after an Apify actor finishes. Use Finished Task Run when the workflow should start after a saved Apify task finishes.
How do I handle large Apify datasets?
Use Fetch Dataset Items after the Apify run finishes. Add a Wait step before fetching data when the same workflow starts the actor or task.
Are Apify workflow steps billed?
Apify usage may include charges from Apify. Kyrios premium workflow usage may also apply depending on your account setup.
What should I do if no Apify data is returned?
Confirm the Apify run completed, verify the selected action, add a Wait step if needed, and test with a small sample.