From 504f31ee6c955313fae882137a525a1badc6ff84 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 2 Jul 2026 19:48:09 +0000 Subject: [PATCH 1/5] docs: fix high and medium inaccuracies in integrations pages - integrating-actors-via-api.md: webhook requestUrl example uses /v2/acts/ prefix (the prefix the Console Actor-integration parser matches), not /v2/actors/. - lindy.md: fix broken rental pricing anchor to the rental page slug and note the rental model is being retired in 2026. - mastra.md: swap Actors via the tools query parameter in the MCP server URL, not a nonexistent actors parameter. - mcp-connectors/using-connectors-in-actors.md: add availability note that the connector picker is gated by a rollout and falls back to text/JSON input. - skyfire.md: minimum PAY token balance is $1, not $5 (three places); remove the Discover payment requirements section (402 discovery is x402-only, not implemented for Skyfire). - webhooks/actions.md: webhook HTTP request timeout is 2 minutes, not 30 seconds. - webhooks/index.md: HTTP POST is not the only action; note Slack, Gmail, Google Drive, and GitHub issue actions. - gumloop/index.md: Console button label is "Save as a new task", not "Create a task". - kestra.md: move input/maxItems onto the run task, fix datasetId to reference the run output, and fix the log task placement to be below get_dataset. - slack.md: attribution links to the integration settings page in Apify Console, not apify.com; list all eight ACTOR_JOB_STATUSES for runs and builds. --- .../actors/integrating-actors-via-api.md | 2 +- sources/platform/integrations/ai/lindy.md | 4 ++-- sources/platform/integrations/ai/mastra.md | 2 +- .../using-connectors-in-actors.md | 6 ++++++ sources/platform/integrations/ai/skyfire.md | 19 +++---------------- .../programming/webhooks/actions.md | 2 +- .../programming/webhooks/index.md | 4 ++-- .../gumloop/index.md | 2 +- .../workflows-and-notifications/kestra.md | 10 +++++----- .../workflows-and-notifications/slack.md | 6 +++--- 10 files changed, 25 insertions(+), 32 deletions(-) diff --git a/sources/platform/integrations/actors/integrating-actors-via-api.md b/sources/platform/integrations/actors/integrating-actors-via-api.md index b53238d752..fc9601a126 100644 --- a/sources/platform/integrations/actors/integrating-actors-via-api.md +++ b/sources/platform/integrations/actors/integrating-actors-via-api.md @@ -22,7 +22,7 @@ The webhook should look something like this: ```json5 { - "requestUrl": "https://api.apify.com/v2/actors//runs", + "requestUrl": "https://api.apify.com/v2/acts//runs", "eventTypes": ["ACTOR.RUN.SUCCEEDED"], "condition": { "actorId": "", diff --git a/sources/platform/integrations/ai/lindy.md b/sources/platform/integrations/ai/lindy.md index b52c066d88..4c2b42b51f 100644 --- a/sources/platform/integrations/ai/lindy.md +++ b/sources/platform/integrations/ai/lindy.md @@ -46,9 +46,9 @@ This section demonstrates how to integrate Apify's data extraction capabilities ![Apify "Run Actor" module configuration in Lindy, showing a dropdown or search for Actors, with "Instagram profile scraper" selected.](images/lindy/lindy-instagram-actor.png) -:::tip Actor Availability +:::tip Actor availability -You have access to thousands of Actors available on the [Apify Store](https://apify.com/store). Please note that Actors using the _rental pricing model_ are not available for use with this integration. For details on Actor pricing models, refer to our [Pricing Documentation](/platform/actors/publishing/monetize#rental-pricing-model). +You have access to thousands of Actors available on the [Apify Store](https://apify.com/store). Please note that Actors using the _rental pricing model_ are not available for use with this integration. The rental pricing model is being retired during 2026 and migrated to pay-per-usage. For details, refer to our [rental pricing model documentation](/platform/actors/publishing/monetize/rental). ::: diff --git a/sources/platform/integrations/ai/mastra.md b/sources/platform/integrations/ai/mastra.md index 29d848509d..69ff6bc084 100644 --- a/sources/platform/integrations/ai/mastra.md +++ b/sources/platform/integrations/ai/mastra.md @@ -116,7 +116,7 @@ await mcpClient.disconnect(); :::note Use any Apify Actor -Since it uses the [Apify MCP server](https://mcp.apify.com), swap in any Apify Actor from the [Apify Store](https://apify.com/store) by updating the startup request’s `actors` parameter. +Since it uses the [Apify MCP server](https://mcp.apify.com), swap in any Apify Actor from the [Apify Store](https://apify.com/store) by adding it to the `tools` query parameter in the server URL (for example, `https://mcp.apify.com/?tools=apify/rag-web-browser`). No other changes are needed in the agent code. ::: diff --git a/sources/platform/integrations/ai/mcp-connectors/using-connectors-in-actors.md b/sources/platform/integrations/ai/mcp-connectors/using-connectors-in-actors.md index 45196fdc22..d5d77d80ec 100644 --- a/sources/platform/integrations/ai/mcp-connectors/using-connectors-in-actors.md +++ b/sources/platform/integrations/ai/mcp-connectors/using-connectors-in-actors.md @@ -14,6 +14,12 @@ This guide explains how to build Actors that accept [MCP connectors](/platform/i To accept MCP connectors as input, set `resourceType: "mcpConnector"` on the input field. This renders a connector picker in Apify Console and enforces which connectors are compatible with the Actor. +:::note Availability + +MCP connector support is rolling out gradually and is not yet enabled for all accounts. If the connector picker does not appear in Apify Console, the feature is not yet available for you. Until then, a `mcpConnector` field of type `string` falls back to a plain text input and a field of type `array` falls back to a JSON editor. + +::: + ### Single connector For an Actor that uses one connector, set `type` to `string`: diff --git a/sources/platform/integrations/ai/skyfire.md b/sources/platform/integrations/ai/skyfire.md index 245fd511a4..00d1369db7 100644 --- a/sources/platform/integrations/ai/skyfire.md +++ b/sources/platform/integrations/ai/skyfire.md @@ -112,14 +112,14 @@ Replace `YOUR_SKYFIRE_API_KEY` with Skyfire buyer API key, which you can obtain When an agent uses the Apify MCP server with Skyfire payments, the workflow proceeds as follows: 1. The agent searches for suitable Actors using the search tools or works with pre-loaded Actors. -1. When attempting to run an Actor, the agent recognizes the need for a Skyfire PAY token with a minimum of $5 and calls the Skyfire MCP server to create it. +1. When attempting to run an Actor, the agent recognizes the need for a Skyfire PAY token with a minimum of $1 and calls the Skyfire MCP server to create it. 1. The agent calls the Actor tool with the payment token. 1. The Apify platform validates the token and starts the Actor run. 1. The Actor does the work and delivers results. 1. When the run completes, the agent receives the Actor results and can retrieve additional data if needed. 1. Finally, Apify's billing system charges the Skyfire PAY token for the actual usage cost. -Any unused funds remain available in the token for future runs or are returned to your Skyfire wallet when the token expires. This means you will not lose money if the actual usage is less than the $5 minimum. +Any unused funds remain available in the token for future runs or are returned to your Skyfire wallet when the token expires. This means you will not lose money if the actual usage is less than the $1 minimum. ![The flow](../images/skyfire-apify-agentic-flow.png) @@ -156,19 +156,6 @@ Instead of using a traditional Apify API token, pass your Skyfire PAY token in t skyfire-pay-id: YOUR_SKYFIRE_PAY_TOKEN ``` -### Discover payment requirements - -To learn the Skyfire-specific payment details before paying, call the endpoint without a token and add the `X-APIFY-PAYMENT-PROTOCOL: SKYFIRE` header. The API responds with HTTP `402` and the Skyfire payment requirements, which you use to create a PAY token. - -```bash -curl -si \ - -H 'X-APIFY-PAYMENT-PROTOCOL: SKYFIRE' \ - 'https://api.apify.com/v2/actors/ACTOR_ID/run-sync-get-dataset-items' -# → HTTP 402 with the Skyfire payment requirements -``` - -Once you send the `skyfire-pay-id` header, the protocol is inferred from it, so you no longer need to include `X-APIFY-PAYMENT-PROTOCOL`. - ### Run an Actor Make a standard Actor run request to the [run Actor endpoint](https://docs.apify.com/api/v2#/reference/actors/run-collection/run-actor), but include the Skyfire PAY token in the header. @@ -221,7 +208,7 @@ https://api.apify.com/v2/store?allowsAgenticUsers=true ### Payment requirements -Your Skyfire PAY token must have at least _$5_ available to run Actors. However, you will only be charged for actual usage. If an Actor run costs less than 5$, the unused funds remain available in your token for future runs or return to your Skyfire wallet when the token expires. +Your Skyfire PAY token must have at least _$1_ available to run Actors. However, you will only be charged for actual usage. If an Actor run costs less than $1, the unused funds remain available in your token for future runs or return to your Skyfire wallet when the token expires. ### Unsupported features diff --git a/sources/platform/integrations/programming/webhooks/actions.md b/sources/platform/integrations/programming/webhooks/actions.md index 40933972f6..18bff66521 100644 --- a/sources/platform/integrations/programming/webhooks/actions.md +++ b/sources/platform/integrations/programming/webhooks/actions.md @@ -51,7 +51,7 @@ You can also use [Headers template](/platform/integrations/webhooks/actions#head ::: -Note that webhook HTTP requests have a timeout of _30 seconds_. +Note that webhook HTTP requests have a timeout of _2 minutes_. If your endpoint performs a time-consuming operation, respond to the request immediately to prevent timeouts before Apify receives the response. To ensure reliable completion of the time-consuming operation, consider using a message queue internally to retry the operation on internal failure. In rare cases, the webhook might be invoked more than once. diff --git a/sources/platform/integrations/programming/webhooks/index.md b/sources/platform/integrations/programming/webhooks/index.md index 2148788956..bb7c014d2b 100644 --- a/sources/platform/integrations/programming/webhooks/index.md +++ b/sources/platform/integrations/programming/webhooks/index.md @@ -13,9 +13,9 @@ You can find webhooks under the **Integrations** tab on an Actor's page in [Apif To define a webhook, select a system **event** that triggers the webhook. Then, provide the **action** to execute after the event. When the event occurs, the system executes the action. -:::info Current webhook limitations +:::info Webhook actions - Currently, the only available action is to send a POST HTTP request to a URL specified in the webhook. +The most common action is to send a POST HTTP request to a URL specified in the webhook. Webhooks can also trigger other actions, such as sending a Slack message, an email through Gmail, a file to Google Drive, or creating a GitHub issue. ::: diff --git a/sources/platform/integrations/workflows-and-notifications/gumloop/index.md b/sources/platform/integrations/workflows-and-notifications/gumloop/index.md index 95d1838c8b..c8fdd63a41 100644 --- a/sources/platform/integrations/workflows-and-notifications/gumloop/index.md +++ b/sources/platform/integrations/workflows-and-notifications/gumloop/index.md @@ -71,7 +71,7 @@ To use the Apify integration in Gumloop, you need an Apify account, a Gumloop ac 1. _Create and save tasks in Apify_ - The Apify Task Runner node fetches tasks from your saved tasks in Apify Console. To create a task, navigate to [**Actors**](https://console.apify.com/actors), click on the Actor you want to use, and then click **Create a task** next to the Run button. Configure your task settings and save. + The Apify Task Runner node fetches tasks from your saved tasks in Apify Console. To create a task, navigate to [**Actors**](https://console.apify.com/actors), click on the Actor you want to use, and then click **Save as a new task** next to the Run button. Configure your task settings and save. ![Create a task on an Actor](images/create_apify_task.png) diff --git a/sources/platform/integrations/workflows-and-notifications/kestra.md b/sources/platform/integrations/workflows-and-notifications/kestra.md index 626941780f..5d6dc47dc6 100644 --- a/sources/platform/integrations/workflows-and-notifications/kestra.md +++ b/sources/platform/integrations/workflows-and-notifications/kestra.md @@ -37,12 +37,12 @@ Tasks allow you to perform operations like running an Actor within a workflow. 1. Configure the `run_apify_actor` task by adding your required values for the properties listed below: - `actorId`: Actor ID or a tilde-separated owner's username and Actor name. - `apiToken`: A reference to the secret value you set up earlier. For example "\{\{secret(namespace=flow.namespace, key='APIFY_API_KEY')\}\}" -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')\}\}" - `input`: Input for the Actor run. The input is optional and can be used to pass data to the Actor. For our example we will add 'hashtags: ["fyp"]' - - `maxItems`: The maximum number of items to fetch from the dataset. For our example we will set this to 5. -1. Now add the final task to log the output of the dataset. Add a new task below the `log_output` with an ID of `log_output` and a type of `io.kestra.plugin.core.log.Log`. + - `maxItems`: The maximum number of items to fetch. For our example we will set this to 5. +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: "\{\{outputs.run_apify_actor.defaultDatasetId\}\}" +1. Now add the final task to log the output of the dataset. Add a new task below the `get_dataset` with an ID of `log_output` and a type of `io.kestra.plugin.core.log.Log`. 1. Configure the `log_output` task to log the output of the dataset by configuring the following values: - `message`: The message to log. You can use the value from the previous task using the following syntax: '\{\{outputs.get_dataset.dataset\}\}' 1. Now save and run your flow. diff --git a/sources/platform/integrations/workflows-and-notifications/slack.md b/sources/platform/integrations/workflows-and-notifications/slack.md index 55c2755d12..d1ac086fb0 100644 --- a/sources/platform/integrations/workflows-and-notifications/slack.md +++ b/sources/platform/integrations/workflows-and-notifications/slack.md @@ -54,7 +54,7 @@ A few rules apply to every template: - The template must be between 2 and 4000 characters long. - The text supports [Slack's mrkdwn syntax](https://api.slack.com/reference/surfaces/formatting), which uses single-asterisk bold (`*bold*`) and `` for links rather than the standard Markdown `[label](url)`. -- Apify automatically appends a "Sent by Apify" attribution line that links to apify.com, so you don't need to add one yourself. +- Apify automatically appends a "Sent by Apify" attribution line that links to the integration's settings page in Apify Console, so you don't need to add one yourself. - `TEST` events ignore the template and post a fixed test message. Use them to verify channel delivery. - An empty template falls back to Apify's built-in run-status preset. @@ -126,8 +126,8 @@ For `ACTOR.BUILD.*` events, `resource` is the build document - the same object r The `resource.status` field uses these values: -- Actor run: `READY`, `RUNNING`, `SUCCEEDED`, `FAILED`, `ABORTED`, `TIMED-OUT`, `ABORTING`. -- Actor build: `READY`, `RUNNING`, `SUCCEEDED`, `FAILED`, `ABORTED`, `TIMED-OUT`. +- Actor run: `READY`, `RUNNING`, `SUCCEEDED`, `FAILED`, `TIMING-OUT`, `TIMED-OUT`, `ABORTING`, `ABORTED`. +- Actor build: `READY`, `RUNNING`, `SUCCEEDED`, `FAILED`, `TIMING-OUT`, `TIMED-OUT`, `ABORTING`, `ABORTED`. :::tip Full resource object From 7ab89b369a9955361f61510fb85fbbad6f404585 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 2 Jul 2026 20:21:53 +0000 Subject: [PATCH 2/5] docs: address review feedback on integrations PR - integrating-actors-via-api.md: keep the /v2/actors/ webhook URL (per maintainer, /v2/acts/ is legacy) - using-connectors-in-actors.md: remove the MCP connector availability note (feature is fully released) --- .../integrations/actors/integrating-actors-via-api.md | 2 +- .../ai/mcp-connectors/using-connectors-in-actors.md | 6 ------ 2 files changed, 1 insertion(+), 7 deletions(-) diff --git a/sources/platform/integrations/actors/integrating-actors-via-api.md b/sources/platform/integrations/actors/integrating-actors-via-api.md index fc9601a126..b53238d752 100644 --- a/sources/platform/integrations/actors/integrating-actors-via-api.md +++ b/sources/platform/integrations/actors/integrating-actors-via-api.md @@ -22,7 +22,7 @@ The webhook should look something like this: ```json5 { - "requestUrl": "https://api.apify.com/v2/acts//runs", + "requestUrl": "https://api.apify.com/v2/actors//runs", "eventTypes": ["ACTOR.RUN.SUCCEEDED"], "condition": { "actorId": "", diff --git a/sources/platform/integrations/ai/mcp-connectors/using-connectors-in-actors.md b/sources/platform/integrations/ai/mcp-connectors/using-connectors-in-actors.md index d5d77d80ec..45196fdc22 100644 --- a/sources/platform/integrations/ai/mcp-connectors/using-connectors-in-actors.md +++ b/sources/platform/integrations/ai/mcp-connectors/using-connectors-in-actors.md @@ -14,12 +14,6 @@ This guide explains how to build Actors that accept [MCP connectors](/platform/i To accept MCP connectors as input, set `resourceType: "mcpConnector"` on the input field. This renders a connector picker in Apify Console and enforces which connectors are compatible with the Actor. -:::note Availability - -MCP connector support is rolling out gradually and is not yet enabled for all accounts. If the connector picker does not appear in Apify Console, the feature is not yet available for you. Until then, a `mcpConnector` field of type `string` falls back to a plain text input and a field of type `array` falls back to a JSON editor. - -::: - ### Single connector For an Actor that uses one connector, set `type` to `string`: From a73df2fa79497dad6b289c3ff4fd07e0e3d6e2fc Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 2 Jul 2026 20:27:01 +0000 Subject: [PATCH 3/5] docs: make webhook actions list grammatically parallel --- sources/platform/integrations/programming/webhooks/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/platform/integrations/programming/webhooks/index.md b/sources/platform/integrations/programming/webhooks/index.md index bb7c014d2b..98b371daa5 100644 --- a/sources/platform/integrations/programming/webhooks/index.md +++ b/sources/platform/integrations/programming/webhooks/index.md @@ -15,7 +15,7 @@ To define a webhook, select a system **event** that triggers the webhook. Then, :::info Webhook actions -The most common action is to send a POST HTTP request to a URL specified in the webhook. Webhooks can also trigger other actions, such as sending a Slack message, an email through Gmail, a file to Google Drive, or creating a GitHub issue. +The most common action is to send a POST HTTP request to a URL specified in the webhook. Webhooks can also trigger other actions, such as posting a Slack message, sending an email through Gmail, uploading a file to Google Drive, or creating a GitHub issue. ::: From 26fbac90e86641f09b130760f27ebe346686f479 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 2 Jul 2026 21:29:07 +0000 Subject: [PATCH 4/5] docs: keep Skyfire MCP minimum at $5 Per maintainer clarification, the API-level minimum is $1 but the MCP integration deliberately requires a $5 minimum PAY token to buffer reuse across a session. This page documents the MCP flow, so revert to $5. --- sources/platform/integrations/ai/skyfire.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sources/platform/integrations/ai/skyfire.md b/sources/platform/integrations/ai/skyfire.md index 00d1369db7..f1a5f83df6 100644 --- a/sources/platform/integrations/ai/skyfire.md +++ b/sources/platform/integrations/ai/skyfire.md @@ -112,14 +112,14 @@ Replace `YOUR_SKYFIRE_API_KEY` with Skyfire buyer API key, which you can obtain When an agent uses the Apify MCP server with Skyfire payments, the workflow proceeds as follows: 1. The agent searches for suitable Actors using the search tools or works with pre-loaded Actors. -1. When attempting to run an Actor, the agent recognizes the need for a Skyfire PAY token with a minimum of $1 and calls the Skyfire MCP server to create it. +1. When attempting to run an Actor, the agent recognizes the need for a Skyfire PAY token with a minimum of $5 and calls the Skyfire MCP server to create it. 1. The agent calls the Actor tool with the payment token. 1. The Apify platform validates the token and starts the Actor run. 1. The Actor does the work and delivers results. 1. When the run completes, the agent receives the Actor results and can retrieve additional data if needed. 1. Finally, Apify's billing system charges the Skyfire PAY token for the actual usage cost. -Any unused funds remain available in the token for future runs or are returned to your Skyfire wallet when the token expires. This means you will not lose money if the actual usage is less than the $1 minimum. +Any unused funds remain available in the token for future runs or are returned to your Skyfire wallet when the token expires. This means you will not lose money if the actual usage is less than the $5 minimum. ![The flow](../images/skyfire-apify-agentic-flow.png) @@ -208,7 +208,7 @@ https://api.apify.com/v2/store?allowsAgenticUsers=true ### Payment requirements -Your Skyfire PAY token must have at least _$1_ available to run Actors. However, you will only be charged for actual usage. If an Actor run costs less than $1, the unused funds remain available in your token for future runs or return to your Skyfire wallet when the token expires. +Your Skyfire PAY token must have at least _$5_ available to run Actors. However, you will only be charged for actual usage. If an Actor run costs less than $5, the unused funds remain available in your token for future runs or return to your Skyfire wallet when the token expires. ### Unsupported features From e51776220aad96c96106e2542186e8bdee60e967 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 3 Jul 2026 06:54:58 +0000 Subject: [PATCH 5/5] docs: address integrations review feedback - kestra.md: revert to original (keep whole file unchanged, per maintainer) - webhooks/index.md: revert to original (only HTTP POST is documented here; other actions are managed separately) - skyfire.md: restore the 'Discover payment requirements' section --- sources/platform/integrations/ai/skyfire.md | 15 ++++++++++++++- .../integrations/programming/webhooks/index.md | 4 ++-- .../workflows-and-notifications/kestra.md | 10 +++++----- 3 files changed, 21 insertions(+), 8 deletions(-) diff --git a/sources/platform/integrations/ai/skyfire.md b/sources/platform/integrations/ai/skyfire.md index f1a5f83df6..245fd511a4 100644 --- a/sources/platform/integrations/ai/skyfire.md +++ b/sources/platform/integrations/ai/skyfire.md @@ -156,6 +156,19 @@ Instead of using a traditional Apify API token, pass your Skyfire PAY token in t skyfire-pay-id: YOUR_SKYFIRE_PAY_TOKEN ``` +### Discover payment requirements + +To learn the Skyfire-specific payment details before paying, call the endpoint without a token and add the `X-APIFY-PAYMENT-PROTOCOL: SKYFIRE` header. The API responds with HTTP `402` and the Skyfire payment requirements, which you use to create a PAY token. + +```bash +curl -si \ + -H 'X-APIFY-PAYMENT-PROTOCOL: SKYFIRE' \ + 'https://api.apify.com/v2/actors/ACTOR_ID/run-sync-get-dataset-items' +# → HTTP 402 with the Skyfire payment requirements +``` + +Once you send the `skyfire-pay-id` header, the protocol is inferred from it, so you no longer need to include `X-APIFY-PAYMENT-PROTOCOL`. + ### Run an Actor Make a standard Actor run request to the [run Actor endpoint](https://docs.apify.com/api/v2#/reference/actors/run-collection/run-actor), but include the Skyfire PAY token in the header. @@ -208,7 +221,7 @@ https://api.apify.com/v2/store?allowsAgenticUsers=true ### Payment requirements -Your Skyfire PAY token must have at least _$5_ available to run Actors. However, you will only be charged for actual usage. If an Actor run costs less than $5, the unused funds remain available in your token for future runs or return to your Skyfire wallet when the token expires. +Your Skyfire PAY token must have at least _$5_ available to run Actors. However, you will only be charged for actual usage. If an Actor run costs less than 5$, the unused funds remain available in your token for future runs or return to your Skyfire wallet when the token expires. ### Unsupported features diff --git a/sources/platform/integrations/programming/webhooks/index.md b/sources/platform/integrations/programming/webhooks/index.md index 98b371daa5..2148788956 100644 --- a/sources/platform/integrations/programming/webhooks/index.md +++ b/sources/platform/integrations/programming/webhooks/index.md @@ -13,9 +13,9 @@ You can find webhooks under the **Integrations** tab on an Actor's page in [Apif To define a webhook, select a system **event** that triggers the webhook. Then, provide the **action** to execute after the event. When the event occurs, the system executes the action. -:::info Webhook actions +:::info Current webhook limitations -The most common action is to send a POST HTTP request to a URL specified in the webhook. Webhooks can also trigger other actions, such as posting a Slack message, sending an email through Gmail, uploading a file to Google Drive, or creating a GitHub issue. + Currently, the only available action is to send a POST HTTP request to a URL specified in the webhook. ::: diff --git a/sources/platform/integrations/workflows-and-notifications/kestra.md b/sources/platform/integrations/workflows-and-notifications/kestra.md index 5d6dc47dc6..626941780f 100644 --- a/sources/platform/integrations/workflows-and-notifications/kestra.md +++ b/sources/platform/integrations/workflows-and-notifications/kestra.md @@ -37,12 +37,12 @@ Tasks allow you to perform operations like running an Actor within a workflow. 1. Configure the `run_apify_actor` task by adding your required values for the properties listed below: - `actorId`: Actor ID or a tilde-separated owner's username and Actor name. - `apiToken`: A reference to the secret value you set up earlier. For example "\{\{secret(namespace=flow.namespace, key='APIFY_API_KEY')\}\}" - - `input`: Input for the Actor run. The input is optional and can be used to pass data to the Actor. For our example we will add 'hashtags: ["fyp"]' - - `maxItems`: The maximum number of items to fetch. For our example we will set this to 5. -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. 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: "\{\{outputs.run_apify_actor.defaultDatasetId\}\}" -1. Now add the final task to log the output of the dataset. Add a new task below the `get_dataset` with an ID of `log_output` and a type of `io.kestra.plugin.core.log.Log`. + - `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')\}\}" + - `input`: Input for the Actor run. The input is optional and can be used to pass data to the Actor. For our example we will add 'hashtags: ["fyp"]' + - `maxItems`: The maximum number of items to fetch from the dataset. For our example we will set this to 5. +1. Now add the final task to log the output of the dataset. Add a new task below the `log_output` with an ID of `log_output` and a type of `io.kestra.plugin.core.log.Log`. 1. Configure the `log_output` task to log the output of the dataset by configuring the following values: - `message`: The message to log. You can use the value from the previous task using the following syntax: '\{\{outputs.get_dataset.dataset\}\}' 1. Now save and run your flow.