Skip to content

docs: add Apify to recommended proxy services - #5020

Draft
Jakub-Vacek wants to merge 2 commits into
triggerdotdev:mainfrom
apify:feat/734-add-apify-to-the-recommended-providers-list
Draft

Jakub-Vacek wants to merge 2 commits into
triggerdotdev:mainfrom
apify:feat/734-add-apify-to-the-recommended-providers-list

Conversation

@Jakub-Vacek

Copy link
Copy Markdown

Pre-agreed with the Trigger.dev team on Discord: https://discord.com/channels/1066956501299777596/1534928934184157205

✅ Checklist

  • I have followed every step in the contributing guide
  • The PR title follows the convention.
  • I ran and tested the code works

Testing

  • Ran npx mintlify broken-links in docs/: no broken links found.
  • Ran the docs locally (npm run dev in docs/, port 3050) and checked the Proxying section on /guides/examples/puppeteer: Apify renders first in the list and links to https://apify.com/.

Changelog

Added Apify to the recommended proxy services list in the Proxying section of the Puppeteer example (docs/guides/examples/puppeteer.mdx). Trigger.dev Cloud requires third-party scraping to be proxied, and Apify runs requests on its own infrastructure. One line, alphabetical order, same format as the existing entries.


Screenshots

obrazek

💯

@changeset-bot

changeset-bot Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 29960c1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 99840ec7-7b5a-4481-bfc2-74a2e1e922ae
📥 Commits

Reviewing files that changed from the base of the PR and between d38af86 and 29960c1.

📒 Files selected for processing: 1
  • docs/guides/examples/puppeteer.mdx
🚧 Files skipped from review as they are similar to previous changes: 1
  • docs/guides/examples/puppeteer.mdx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

Walkthrough

The Puppeteer guide now includes Apify in its list of recommended proxy services.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to 29960

No issue requiring a change before merging is identified in the Apify recommendation.

Pre-merge checks: Passed 5
Check name Status Explanation
Description check Passed The description covers the checklist, testing steps, changelog, and screenshots. It clearly explains the documentation change and provides validation details. It does not include a linked issue, but t…
Title check Passed The title clearly and concisely describes the main change: adding Apify to the recommended proxy services documentation.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

The description covers the checklist, testing steps, changelog, and screenshots. It clearly explains the documentation change and provides validation details. It does not include a linked issue, but the description is otherwise complete.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants