Repository navigation
Conversation
daveomri
marked this pull request as ready for review
October 19, 2026 08:44
…mri/apify-docs into docs/trigger-dot-dev-docs
Use US spelling and clearer link text. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
marcel-rbro
reviewed
Oct 21, 2026
marcel-rbro
left a comment
marcel-rbro
left a comment
Contributor
There was a problem hiding this comment.
I pushed a commit with small nits: US spelling, link text, and one rephrased sentence. The description mentions hub cards, but index.mdx isn't changed, so trigger-dev.svg and trigger-dev-white.svg aren't used anywhere. Did you mean to add a card, or should the logos be dropped?
|
|
||
| For anything longer than a few seconds, start the Actor with `start()` instead of `call()` and attach an [ad-hoc webhook](/integrations/webhooks/ad-hoc-webhooks) that points at a Trigger.dev [wait token](https://trigger.dev/docs/wait-for-token) URL. The task suspends on `wait.forToken()`, and Apify resumes it by calling the URL when the Actor run ends. A suspended task doesn't count toward Trigger.dev compute usage, however long the Actor runs. | ||
|
|
||
| The full task is in Trigger.dev's [Apify Actor run guide](https://trigger.dev/docs/guides/examples/apify-actor-run#example-2-run-a-long-actor-and-resume-on-a-webhook). It relies on these Apify details: |
Contributor
There was a problem hiding this comment.
This guide still returns a 404 because it's in review in triggerdotdev/trigger.dev#5021, so we'll need to hold this PR until that merges.
|
|
||
| ## Use Apify as an agent tool | ||
|
|
||
| Trigger.dev [AI chat agents](https://trigger.dev/docs/ai-chat/tools) use [AI SDK](https://ai-sdk.dev/) tools, so Apify can be a set of tools the agent calls. Trigger.dev's [Apify tools example](https://trigger.dev/docs/ai-chat/tools#example-web-scraping-tools-with-apify) has the full code for three tools: |
Contributor
There was a problem hiding this comment.
I can't find the #example-web-scraping-tools-with-apify section on the live page or in any open Trigger.dev PR, so where will the full code for these tools live?
Collaborator
Author
There was a problem hiding this comment.
This branch has not been deployed
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
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.
Adds a Trigger.dev integration page with the logo and hub cards, covering when to wait for an Actor run, when to resume on an ad-hoc webhook, and how to use Apify as an agent tool.
The samples were run against a live Apify account, and the full code for the webhook and agent patterns is linked from the Trigger.dev docs.