Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Epic] Document the Web Fetch action across integrations

Abierto
  • ¿Algo no está bien?
#2,879 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@marcel-rbro ya está trabajando en esto.

Desde el 21/8/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

medium priority product enhancement t-integrations

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.

Lenguaje dominante
JavaScript
Estrellas
82
Forks
240
Merge medio
4 d 2 h
PR fusionados (30 d)
44

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apify/apify-docs

Todos los issues de apify/apify-docs

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.