apify · mtrunkat · Jul 2, 2026 · Jul 2, 2026 · Jul 2, 2026 · Jul 2, 2026
@@ -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).
 
 :::
 

@@ -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.
 
 :::

@@ -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 _$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
 

@@ -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.

@@ -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 posting a Slack message, sending an email through Gmail, uploading a file to Google Drive, or creating a GitHub issue.
 
 :::
 

@@ -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)
 

@@ -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.

@@ -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 `<url|label>` 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