-
Notifications
You must be signed in to change notification settings - Fork 126
docs: add page for Kestra integration #1917
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
sources/platform/integrations/workflows-and-notifications/kestra.md
Outdated
Show resolved
Hide resolved
sources/platform/integrations/workflows-and-notifications/kestra.md
Outdated
Show resolved
Hide resolved
1. Add a new task below the **run_apify_actor** with an ID of **get_dataset** and a type of **io.kestra.plugin.apify.dataset.Get**.: | ||
1. Configure the **get_dataset** to fetch the dataset generated by the **run_apify_actor** task by configuring the following values: | ||
- **datasetId**: The ID of the dataset to fetch. You can use the value from the previous task using the following syntax: "\{\{secret(namespace=flow.namespace, key='APIFY_API_KEY')\}\}" | ||
- **apiToken**: A reference to the secret value you set up earlier. For example '\{\{secret(namespace=flow.namespace, key='APIFY_API_KEY')\}\}' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like apiToken
made it in here twice.
sources/platform/integrations/workflows-and-notifications/kestra.md
Outdated
Show resolved
Hide resolved
sources/platform/integrations/workflows-and-notifications/kestra.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for having added this doc!
docs: fix typos in docs. Co-authored-by: AJ Emerich <[email protected]>
Thank you all for the feedback. I've committed all of the suggested changes. I noticed that their is also a reference to the docs and repos for other integrations on the Integrate with Apify page so I've added a reference to Kestra as well. @fdelbrayelle are you able to confirm that the Kestra documentation for Apify will eventually be available from the link bellow? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, please have a team admin upgrade your team to Bugbot Pro by visiting the Cursor dashboard. Your first 14 days will be free!
Comment @cursor review
or bugbot run
to trigger another review on this PR
- id: get_data_set_raw | ||
type: io.kestra.plugin.apify.dataset.Get | ||
datasetId: '{{outputs.run_actor.defaultDatasetId}}' | ||
apiToken: "{{secret(namespace=flow.namespace, key='APIFY_API_KEY')}}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: YAML Configuration Errors in Kestra Guide
The example YAML in the Kestra integration guide has a few issues. The maxItems
property is incorrectly placed under the actor.Run
task, where it will likely be ignored or cause errors, as it's intended for dataset fetching operations. Additionally, the apiToken
property is redundantly specified for both tasks, which could lead to confusion.
Yes @ammeek correct! @aj-emerich It will be from 1.1, won't it? |
Yeah that looks correct. |
I've wrote a short guide that shows how to use Apify from Kestra flows (running Actors, getting the last run, fetching datasets as files or structured JSON, and a simple example flow). It includes:
A friendly intro to Kestra + why it pairs nicely with Apify
Authentication notes (API key + Kestra Secrets)
A step-by-step example flow and a copy-paste YAML you can run in Kestra
Links to the plugin repo and relevant docs, plus a small troubleshooting section
Please let me know if any changes are required.