Conversation
There was a problem hiding this comment.
Pull request overview
Adds documentation and assets for a new viaSocket integration page and exposes it from the Integrations landing page.
Changes:
- Added a new viaSocket integration doc under Workflows & notifications.
- Added a viaSocket logo asset and surfaced viaSocket as a card on the Integrations index.
- Added a viaSocket UI screenshot asset used by the new doc.
Reviewed changes
Copilot reviewed 2 out of 9 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| static/img/platform/integrations/viasocket.ico | Adds a viaSocket logo asset for the integrations cards. |
| sources/platform/integrations/workflows-and-notifications/viasocket.md | New step-by-step integration guide for viaSocket. |
| sources/platform/integrations/index.mdx | Adds a viaSocket card entry in “Integration platforms”. |
| sources/platform/integrations/images/viasocket/viasocket-gmail-action.png | Adds a screenshot referenced by the new viaSocket guide. |
| 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. | ||
|
|
There was a problem hiding this comment.
This integration doc is missing the standard third‑party integration disclaimer used across other files in workflows-and-notifications (e.g., zapier.md imports @site/sources/_partials/_third-party-integration.mdx and renders <ThirdPartyDisclaimer />). Please add the same import right after front matter and render the disclaimer near the top of the page (after the intro), to keep legal/support expectations consistent.
| <Card | ||
| title="viaSocket" | ||
| to="./integrations/viasocket" | ||
| imageUrl="/img/platform/integrations/viasocket.ico" |
There was a problem hiding this comment.
imageUrl points to an .ico file, but all other integration logos in static/img/platform/integrations/ use .svg, .png, .jpeg, or .webp. Consider converting the viaSocket logo to one of the existing formats (preferably .svg or optimized .png) to match established asset conventions and avoid any inconsistent rendering/optimization issues with .ico in docs UI.
| imageUrl="/img/platform/integrations/viasocket.ico" | |
| imageUrl="/img/platform/integrations/viasocket.svg" |
| imageUrl="/img/platform/integrations/zapier.svg" | ||
| smallImage | ||
| /> | ||
| <Card |
There was a problem hiding this comment.
Unfortunately, due to limited space on this page, the cards are reserved for the largest integrations in their respective categories
No description provided.