docs: rewrite Actor-to-Actor integration page#2546
Open
marcel-rbro wants to merge 9 commits into
Open
Conversation
Contributor
|
✅ Preview for this PR (commit |
Refresh the Add an integration flow to match the new integrations dialog in Apify Console. The previous instructions referenced a removed "Apify (Connect Actor or Task)" affordance. Several TODOs remain inline for items that still need confirmation. Refs #2460 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
marcel-rbro
force-pushed
the
docs/actor-to-actor-rewrite
branch
from
d0d9d70 to
779baca
Compare
marcel-rbro
changed the base branch from
docs/integrations-restructure-tiers
to
master
Contributor
|
Python client model regeneration failed. See workflow run. |
- Use "trigger" instead of "fire" for consistency with platform terminology - Drop conversational "still" from the test-run note - Remove emphasis bold from "source" Actor (style guide reserves bold for UI elements) - Replace single "Blog tutorial" link with a "Next steps" section pointing at the two sibling pages plus the blog walkthrough Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Rename page title to "Develop integration-ready Actors" so the developer audience is explicit; add sidebar_label to match - Lead the page with a one-line audience statement and an explicit framing that any Actor can be a target but designed ones provide a better experience - Add a note linking to Integration Actors in Apify Store for inspiration, using the UI term "Integration Actor" for the catalog/category and "integration-ready" only as a descriptive adjective for Actor design - Update the cross-link in the Actor-to-Actor page to match the new sibling title Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
In index.md:
- Replace ambiguous pronoun "It" with explicit "The UI" on the
Implementation details paragraph
In integration_ready_actors.md:
- Remove bold used for emphasis (dataset ID, dataset contents,
"only") - bold reserved for UI elements per style guide
- Drop softening "ideally try to" from the complexity-hiding rule
- Replace first-person plural ("we", "we'd", "we're") with
imperative/second-person voice throughout the Example section
- Fix "fit to memory" -> "fit in memory"
- Clean up field labels (ID instead of Id, "table or collection"
instead of "table / collection")
- Refresh the publishing flow to reference the new "Add integration"
dialog instead of the removed "Connect Actor or task" button
- Fix malformed mailto link (Actor%specific -> Actor%20specific)
- Add inline TODO markers for the stale contact-support listing
workflow and the outdated specific_vs_generic_integrations.png
screenshot, mirroring the TODO convention from index.md
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
marcel-rbro
requested review from
TC-MO and
Copilot
and removed request for
Copilot
TC-MO
reviewed
May 21, 2026
TC-MO
requested changes
May 21, 2026
Contributor
TC-MO
left a comment
TC-MO
left a comment
There was a problem hiding this comment.
Some changes requested, some related to updated content, some cleanup opportunities.
Address review comments on PR #2546: drop the title question mark, remove the stale YouTube embed, refresh the setup-screen labels to match the current Apify Console UI (Start when / Actor input), tighten the variables wording, and normalize capitalization and phrasing in the integration-ready Actors example. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Capture the current Apify Console integration setup screen and embed it under the configuration list so readers can visually anchor the Start when / Actor input / Available variables sections. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Align the title and lead sentence with the sidebar label so the page name matches how it's referenced across the integrations section. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Remove the inline TODOs around "compute units" billing wording and the linked blog post now that both have been confirmed current. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Use "Integrate Actors via API" to match the imperative voice the style guide prefers and align with other action-oriented titles in the section. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
index.mdto match the new integrations dialog in Apify Console; the previous instructions referenced a removed Apify (Connect Actor or Task) affordance<!-- TODO -->markers for items still pending confirmationRefs #2460
This PR is stacked on top of #2506 (
docs/integrations-restructure-tiers). Once that lands, rebase the base tomaster.Outstanding TODOs (to resolve before marking ready)
zExnYbvFoBM) still reflects the current flowintegration-ready-actors.md(specific vs generic distinction) andintegrating-actors-via-api.mdTest plan
pnpm lintpassespnpm buildproduces no broken-link errors for/integrations/actors🤖 Generated with Claude Code