Skip to content

Commit 9626b61

Browse files
committed
chore: removed redundant info
1 parent 5d668e7 commit 9626b61

File tree

1 file changed

+18
-45
lines changed
  • sources/platform/integrations/workflows-and-notifications

1 file changed

+18
-45
lines changed

sources/platform/integrations/workflows-and-notifications/workato.md

Lines changed: 18 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,18 @@
11
---
22
title: Workato integration
3-
description: Learn how to integrate your Apify Actors with Workato to build enterprise-grade automated workflows and connect with hundreds of business applications.
3+
description: Learn how to connect Apify web scraping with Workato to automate data flows across your business applications.
44
sidebar_label: Workato
55
sidebar_position: 7
66
slug: /integrations/workato
77
---
88

9-
**Learn how to integrate your Apify Actors with Workato to build enterprise-grade automated workflows and connect with hundreds of business applications.**
9+
**Learn how to connect Apify web scraping with Workato to automate data flows across your business applications.**
1010

1111
---
1212

13-
[Workato](https://www.workato.com/) is an enterprise-grade integration and automation platform (iPaaS) that enables you to build automated workflows called **"recipes"** across applications using no-code or low-code connectors. With the [Apify Workato Connector](https://apify.com), you can seamlessly integrate web scraping and automation capabilities into your enterprise workflows.
13+
[Workato](https://www.workato.com/) is an enterprise-grade automation platform that lets you build **recipes** (workflows) across applications using no-code connectors. The [Apify Workato Connector](https://apify.com) integrates web scraping capabilities into your enterprise workflows.
1414

15-
Each Workato recipe begins with a **trigger** (an event in one app) and executes one or more **actions** (operations in other apps). The Apify connector provides Apify-specific triggers and actions, allowing you to start or monitor Apify tasks, retrieve scraped data, and incorporate web automation into your business processes.
16-
17-
You can use the Workato integration to trigger workflows when Apify Actors or tasks finish, start scraping jobs based on business events, or fetch and process scraped data across your tech stack.
15+
Recipes start with a **trigger** (an event) and execute **actions** (operations). With the Apify connector, you can start scraping jobs, monitor tasks, and process scraped data throughout your tech stack.
1816

1917
## Get started
2018

@@ -238,27 +236,23 @@ This action provides immediate, on-demand scraping capabilities:
238236

239237
![Scrape Single URL action](../images/workato/scrape-url.png)
240238

241-
## Example use cases
242-
243-
### Automated competitive monitoring
244-
245-
**Trigger:** Scheduled (daily)
246-
**Actions:**
247-
1. Run Actor (competitor price scraper)
248-
1. Get Dataset Items (fetch price data)
249-
1. Send to Google Sheets or Salesforce
250-
1. Send Slack notification if significant price changes detected
251-
252-
### Lead generation from web data
239+
## Long‑running scrapes and async pattern in Workato
253240

254-
**Trigger:** New opportunity created in CRM
255-
**Actions:**
256-
1. Scrape Single URL (extract company data from website)
257-
1. Update CRM record with enriched data
258-
1. Trigger email sequence in marketing automation platform
241+
Long-running scrapes can exceed typical step execution expectations. Use this asynchronous pattern to keep recipes reliable and scalable.
259242

243+
1. Start the run without waiting
244+
- In a recipe, add the **Run Actor** action and configure inputs as needed.
245+
- Run asynchronously (do not block downstream steps on completion).
246+
- ![Run Actor action](../images/workato/run-actor.png)
247+
1. Continue when the run finishes
248+
- Build a separate recipe with the **Actor Run Finished** trigger.
249+
- Filter for the specific Actor or Task you started in Step 1.
250+
- ![Actor Run Finished trigger](../images/workato/trigger-actor.png)
251+
1. Fetch results and process
252+
- In the triggered recipe, add **Get Dataset Items** (use the dataset ID from the trigger payload) and continue processing.
253+
- ![Get Dataset Items action](../images/workato/get-dataset.png)
260254

261-
## Using the integration
255+
## Example use cases
262256

263257
### Data mapping and workflow design
264258

@@ -277,27 +271,6 @@ Workato's visual interface makes it easy to connect Apify data with other busine
277271
- **Rate limiting:** Be mindful of API rate limits when designing high-frequency workflows
278272
- **Data validation:** Validate scraped data before sending to critical business systems
279273

280-
## Long‑running scrapes and async pattern in Workato
281-
282-
Long-running scrapes can exceed typical step execution expectations. Use this asynchronous pattern to keep recipes reliable and scalable.
283-
284-
1. Start the run without waiting
285-
- In a recipe, add the **Run Actor** action and configure inputs as needed.
286-
- Run asynchronously (do not block downstream steps on completion).
287-
- ![Run Actor action](../images/workato/run-actor.png)
288-
1. Continue when the run finishes
289-
- Build a separate recipe with the **Actor Run Finished** trigger.
290-
- Filter for the specific Actor or Task you started in Step 1.
291-
- ![Actor Run Finished trigger](../images/workato/trigger-actor.png)
292-
1. Fetch results and process
293-
- In the triggered recipe, add **Get Dataset Items** (use the dataset ID from the trigger payload) and continue processing.
294-
- ![Get Dataset Items action](../images/workato/get-dataset.png)
295-
296-
:::note Screenshot needed
297-
298-
Please add `../images/workato/async-flow.png` illustrating a two‑recipe setup: one recipe starting a run, and another recipe triggered on run completion.
299-
300-
:::
301274

302275
## Troubleshooting
303276

0 commit comments

Comments
 (0)