Skip to content

Document the Web Fetch action across integrations #2879

Description

@drobnikj

Parent epic: apify/integrations-team#114 · Contract: apify/integrations-team#115

Why?

Ten integration docs pages document "Scrape Single URL" — including advice that only exists because of the old implementation, e.g. dify.md telling users to pick Raw HTTP to stay inside Dify's timeout, and bubble.md warning that Scrape Single URL "may time out if you wait" and prescribing an async workaround. Once the Web Fetch Actor lands, that guidance is wrong.

What?

Update every page that mentions the action, under sources/platform/integrations/:

  • workflows-and-notifications/zapier.md (### Scrape Single URL, ~L114)
  • workflows-and-notifications/n8n/index.md
  • workflows-and-notifications/make/ pages
  • workflows-and-notifications/pipedream.md (~L73)
  • workflows-and-notifications/activepieces.md (~L92, ~L144)
  • workflows-and-notifications/dify.md (~L97 — drop the Raw HTTP timeout workaround)
  • workflows-and-notifications/workato.md (~L173, plus the images/workato/scrape-url.png screenshot)
  • workflows-and-notifications/windmill.md (~L37, ~L205)
  • workflows-and-notifications/ifttt.md (~L128)
  • workflows-and-notifications/bubble.md (~L184, ~L253–265 — the timeout workaround section needs rewriting)

For each: rename the section to Web Fetch, document formats and drop crawlerType, and add a short note that Scrape Single URL is deprecated and points at the new action. Refresh screenshots where the field list is visible.

Camunda and Power Automate document their actions in their own repos (intro.md / README.md) — covered by their own sub-issues, not here.

How?

Do this per platform as each implementation merges, not in one big PR — a docs page describing an action that isn't live yet is worse than a stale one. Keep it as one issue, tick the boxes off.

Metadata

Metadata

Assignees

No one assigned

    Labels

    medium priorityMedium priority issues to be done in a couple of sprints.product enhancementFeatures improving the product.t-integrationsIssues with this label are in the ownership of the integrations team.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions