-
Notifications
You must be signed in to change notification settings - Fork 173
docs: viaSocket integration page added #2276
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
Open
ViaSocket-Git
wants to merge
2
commits into
apify:master
Choose a base branch
from
ViaSocket-Git:viaSocket_integration
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+83
−0
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
77 changes: 77 additions & 0 deletions
77
sources/platform/integrations/workflows-and-notifications/viasocket.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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. | ||
|
|
||
|  | ||
|
|
||
| :::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. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| ## 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. | ||
|
|
||
|  | ||
|
|
||
| ## 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. | ||
|
|
||
|  | ||
|
|
||
| ## 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. | ||
|
|
||
|  | ||
|
|
||
| ## 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. | ||
|
|
||
|  | ||
|
|
||
| If you have any questions or need help, feel free to reach out on the [Apify Discord community](https://discord.com/invite/jyEM2PRvMU). |
Binary file not shown.
Oops, something went wrong.
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.
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.
Broken viaSocket card link path
Medium Severity
The new
viaSocketcard links to/platform/integrations/viasocket, but the new page’sslugis/integrations/viasocket. This mismatch likely produces a 404 from the integrations index and makes the new integration page unreachable via the card.