diff --git a/sources/platform/integrations/images/viasocket-add-trigger.png b/sources/platform/integrations/images/viasocket-add-trigger.png
new file mode 100644
index 0000000000..fb6ebc0803
Binary files /dev/null and b/sources/platform/integrations/images/viasocket-add-trigger.png differ
diff --git a/sources/platform/integrations/images/viasocket-apify-token.png b/sources/platform/integrations/images/viasocket-apify-token.png
new file mode 100644
index 0000000000..17e4be6061
Binary files /dev/null and b/sources/platform/integrations/images/viasocket-apify-token.png differ
diff --git a/sources/platform/integrations/images/viasocket-configure-trigger.png b/sources/platform/integrations/images/viasocket-configure-trigger.png
new file mode 100644
index 0000000000..1c4c9c1f9f
Binary files /dev/null and b/sources/platform/integrations/images/viasocket-configure-trigger.png differ
diff --git a/sources/platform/integrations/images/viasocket-connect-account.png b/sources/platform/integrations/images/viasocket-connect-account.png
new file mode 100644
index 0000000000..fb6ebc0803
Binary files /dev/null and b/sources/platform/integrations/images/viasocket-connect-account.png differ
diff --git a/sources/platform/integrations/images/viasocket-gmail-action.png b/sources/platform/integrations/images/viasocket-gmail-action.png
new file mode 100644
index 0000000000..53710f4085
Binary files /dev/null and b/sources/platform/integrations/images/viasocket-gmail-action.png differ
diff --git a/sources/platform/integrations/images/viasocket-monitor.png b/sources/platform/integrations/images/viasocket-monitor.png
new file mode 100644
index 0000000000..52655eec40
Binary files /dev/null and b/sources/platform/integrations/images/viasocket-monitor.png differ
diff --git a/sources/platform/integrations/images/viasocket-select-trigger.png b/sources/platform/integrations/images/viasocket-select-trigger.png
new file mode 100644
index 0000000000..ba80d3ad2f
Binary files /dev/null and b/sources/platform/integrations/images/viasocket-select-trigger.png differ
diff --git a/sources/platform/integrations/index.mdx b/sources/platform/integrations/index.mdx
index 3b9042f835..ca59ed2598 100644
--- a/sources/platform/integrations/index.mdx
+++ b/sources/platform/integrations/index.mdx
@@ -104,6 +104,12 @@ Apify offers easy-to-set-up solutions for common scenarios, like uploading your
 If you use one of the main integration platforms, Apify's support is here for you. The main advantage of these platforms is that you can integrate Apify into very complex workflows with the choice of thousands of supported services.
 
 <CardGrid>
+    <Card
+        title="viaSocket"
+        to="./integrations/viasocket"
+        imageUrl="/img/platform/integrations/viasocket.ico"
+        smallImage
+    />
     <Card
         title="Make"
         to="./integrations/make"
diff --git a/sources/platform/integrations/workflows-and-notifications/viasocket.md b/sources/platform/integrations/workflows-and-notifications/viasocket.md
new file mode 100644
index 0000000000..43dc1694ac
--- /dev/null
+++ b/sources/platform/integrations/workflows-and-notifications/viasocket.md
@@ -0,0 +1,77 @@
+---
+title: viaSocket integration
+description: Learn how to connect Apify with viaSocket, configure triggers, authenticate using API tokens, and create automation flows.
+sidebar_label: viaSocket
+sidebar_position: 8
+slug: /integrations/viasocket
+---
+
+**Learn how to connect Apify with viaSocket, configure triggers, authenticate using API tokens, and create automation flows.**
+
+---
+
+[viaSocket](https://viasocket.com/) is a workflow automation platform that lets you connect apps and automate tasks without writing code. With the Apify integration, you can trigger Actor runs, retrieve results, and build end-to-end automation pipelines that react to events across your connected apps.
+
+## Step 1: Generate an Apify API token
+
+1. Log in to your [Apify account](https://console.apify.com/).
+1. Go to **Settings > API & Integrations > API Tokens**.
+1. Copy your personal API token.
+
+![Apify API token settings](../images/viasocket-apify-token.png)
+
+:::caution Keep your token secure
+Never share your API token publicly or commit it to version control.
+:::
+
+## Step 2: Create a new flow in viaSocket
+
+1. Log in to your [viaSocket account](https://viasocket.com/) and click **Create New Flow**.
+1. In the **Trigger** section, search for and select **Apify**.
+1. Choose **Finished Task Run** or **Finished Actor Run** as the trigger event.
+
+![Select Apify trigger in viaSocket](../images/viasocket-select-trigger.png)
+![Connect Apify account in viaSocket](../images/viasocket-connect-account.png)
+
+## Step 3: Connect your Apify account
+
+1. Click **Connect to Apify**.
+1. Paste your Apify API token into the connection dialog.
+1. Click **Save** to establish the connection.
+1. Confirm the connection is successfully added before continuing.
+
+![Configure Apify trigger in viaSocket](../images/viasocket-configure-trigger.png)
+
+## Step 4: Configure the trigger
+
+1. Provide the Actor or task ID manually or map it dynamically from a previous step.
+1. Set **Status** to `Succeeded`.
+1. Click **Test** to fetch sample data and verify the trigger works.
+1. Save the trigger configuration.
+
+![Add Apify trigger in viaSocket](../images/viasocket-add-trigger.png)
+
+## Step 5: Add an action
+
+You can add any supported app as the next step in your flow. The example below uses Gmail to send an email when the trigger fires.
+
+1. Click **Add Step**.
+1. Select **Gmail** and choose the **Send Email** action.
+1. Connect or select your Gmail account.
+1. Map the following fields:
+    - **To** - recipient email address
+    - **Subject** - email subject line
+    - **Message Body** - use the trigger `body` object as dynamic input
+1. Click **Test** to run the action and confirm a `200` response status.
+
+![Gmail action configuration in viaSocket](../images/viasocket-gmail-action.png)
+
+## Step 6: Go live and monitor
+
+1. Click **Go Live** and confirm activation.
+1. Use **Flow View** to inspect the flow structure and **Log View** to monitor individual executions.
+1. Re-run a specific execution from **Run History** if needed.
+
+![viaSocket flow monitoring](../images/viasocket-monitor.png)
+
+If you have any questions or need help, feel free to reach out on the [Apify Discord community](https://discord.com/invite/jyEM2PRvMU).
diff --git a/static/img/platform/integrations/viasocket.ico b/static/img/platform/integrations/viasocket.ico
new file mode 100644
index 0000000000..bed9fab606
Binary files /dev/null and b/static/img/platform/integrations/viasocket.ico differ