Connect Viraly to n8n — the open-source, self-hostable workflow automation platform — using the official n8n-nodes-viraly community node. Trigger workflows on Viraly events, or create, update, and publish posts from databases, AI models, internal APIs, and 400+ native n8n integrations. This guide walks you through installing the node, creating credentials, managing the connection from within Viraly, and exploring the available triggers and actions.
Overview
n8n (pronounced “n-eight-n”) is a fair-code workflow automation tool. Unlike Zapier or Make, n8n can be self-hosted on your own infrastructure — so your workflow data never leaves your environment — or run on n8n Cloud. It ships with 400+ native integrations and can execute custom code inside workflows, making it a strong choice for teams that need full data sovereignty or deeply technical automations.
The Viraly integration ships as an official community node published to npm as n8n-nodes-viraly. Once installed into your n8n instance, two nodes become available:
- Viraly Trigger — starts a workflow when a Viraly event occurs (post published, scheduled, failed, new channel, new bio link subscriber)
- Viraly — performs actions against Viraly from anywhere in a workflow (create/update/publish/delete posts, look up channels, list social sets and subscribers)
How the setup works: unlike Slack, Discord, or Microsoft Teams (where setup starts inside Viraly), n8n setup happens inside n8n. You install the community node, create a Viraly credential, and complete an OAuth consent flow from n8n. From that point, n8n stores the access and refresh tokens on its side and handles renewal automatically.
Once connected, you can view the connection status, see what permissions were granted, and revoke access at any time from the n8n integration page inside Viraly (Settings → Integrations → n8n).
Prerequisites
- A Viraly workspace on the Business plan or higher
- An n8n instance — either self-hosted (Docker, npm, or desktop) or n8n Cloud
- Workspace Owner or Admin role in Viraly (to authorize the connection)
- For n8n Cloud: the Viraly node appears automatically when it’s listed as a Verified Community Node on n8n Cloud. If it isn’t yet verified, n8n Cloud does not permit community-node installation and you’ll need to self-host.
Installing the Community Node
Self-hosted n8n
- Open your n8n instance
- Go to Settings → Community Nodes
- Click Install
- Paste
n8n-nodes-viralyinto the npm Package Name field - Read and accept the risks notice (community nodes run arbitrary code — this applies to every community node, not just this one)
- Click Install
- Restart n8n if it doesn’t reload automatically
- Search for “Viraly” in the node picker — you should see the Viraly action and Viraly Trigger
n8n Cloud
Once the Viraly node is listed as a Verified Community Node on n8n Cloud, it appears in the node picker automatically for every Cloud workspace — no install step required. Search for “Viraly” in your scenario canvas.
If it’s not yet verified, n8n Cloud blocks community-node installation. In that case, run a self-hosted n8n instance (Docker is the fastest route) and follow the self-hosted steps above.
Creating Viraly Credentials in n8n
The Viraly node uses OAuth 2.0 with PKCE. Client ID and client secret are baked into the node, so you don’t configure them manually.
- In n8n, go to Credentials → New
- Search for Viraly OAuth2 API and click it
- Leave all fields at their defaults (grant type, authorization URL, access-token URL, client ID, client secret, scopes — all pre-filled)
- Click Connect my account — a new browser tab opens at Viraly’s consent screen
- Sign in to Viraly if prompted, then pick the workspace you want to authorize and click Allow Access
- You’re redirected back to n8n with the credential saved
- Click Save to close the credential editor
The credential is now selectable from any Viraly Trigger or Viraly action node across all your workflows. n8n handles token refresh automatically, so you’ll never need to reconnect as long as the authorization stays valid.
Managing the Connection in Viraly
After you’ve connected, go to Settings → Integrations → n8n inside Viraly. You’ll see:
- Active status — confirms n8n has a valid access token for your workspace
- Connected date — when the connection was first authorized
- Last used — when n8n most recently called the Viraly API
- Granted scopes — the exact permissions you approved (for example
posts:write,channels:read) - Open in n8n — jumps back to your n8n instance
- Disconnect — revokes all n8n tokens for your workspace (see Disconnecting)
You can also see the connection listed at Settings → Connected Apps alongside any other OAuth-based integrations you’ve approved.
Available Triggers
Triggers are fired by the Viraly Trigger node. n8n polls Viraly at the interval you configure on the node (every minute by default on self-hosted; minimum interval depends on your n8n Cloud plan).
- New Post Published — a post was successfully published to a social platform
- New Post Scheduled — a post was scheduled for future publishing
- Post Failed — a post failed to publish
- New Channel Connected — a new social account was connected to the workspace
- New Bio Link Subscriber — someone submitted the email capture form on a Viraly bio link page
Available Actions
Actions are performed by the Viraly node. Pick a Resource (Post, Channel, Social Set, or Subscriber) and then an Operation within that resource.
- Post: Create, Update, Publish Now, Delete, Get, List
- Channel: Get, List
- Social Set: List
- Subscriber: List (by bio link page)
The Create Post operation is platform-agnostic: you supply caption, channelId, and optional schedule info, and Viraly builds the correct platform-specific config (Facebook, Instagram, Twitter/X, LinkedIn, TikTok, Pinterest, YouTube, Threads, Bluesky, Mastodon) server-side.
Example Workflows
- Auto-schedule from RSS: RSS Feed Trigger → Viraly (Create Post, scheduled)
- Slack alert on failed post: Viraly Trigger (Post Failed) → Slack (send channel message)
- Sync bio link subscribers to multiple tools: Viraly Trigger (New Bio Link Subscriber) → Switch → Google Sheets append AND Mailchimp add-to-list AND Klaviyo profile-create
- Local LLM content pipeline (self-hosted): Airtable Trigger → Ollama (generate captions) → Viraly (Create Post, schedule at staggered times)
- Content audit log to Notion: Viraly Trigger (New Post Published) → Notion (create database row with channel, caption, scheduled time, platform metrics)
Disconnecting
You can revoke n8n’s access to your Viraly workspace from inside Viraly — you don’t need to go to n8n to do it.
- In Viraly, go to Settings → Integrations → n8n
- Click Disconnect in the status card
- Confirm in the dialog
Revocation is immediate. Any active workflows using the credential will start failing with authentication errors on their next run. n8n will show a red error badge on affected nodes; you can reconnect by editing the Viraly credential in n8n and re-completing the OAuth flow.
The Settings → Connected Apps page also has a Revoke button that does the same thing.
Troubleshooting
“Viraly” doesn’t appear in the node picker after install
Restart your n8n instance. Community nodes are loaded at startup; a fresh install without a restart won’t be visible until the process reloads. In Docker, restart the container. In npm-installed n8n, stop and start the n8n process.
If you’re on n8n Cloud and the node still isn’t there, the Viraly node is not yet on the Verified Community Nodes list. n8n Cloud does not allow general community-node installation; you’ll need to self-host.
“Authentication failed” during the OAuth flow
This typically means the browser window was closed before you clicked Allow Access, or the consent flow redirected back to n8n while it wasn’t listening. Delete the half-created credential in n8n and try again from scratch — the second attempt usually completes cleanly.
I see “n8n is not connected yet” in Viraly, but I already set it up
Make sure you completed the full consent flow and clicked Save on the credential in n8n. If the browser window closed before you clicked Allow Access, no token was issued. Go back to the n8n credential editor and re-open the Connect my account flow.
If the n8n integration page in Viraly still shows “Not connected” after a successful setup, refresh the browser — the connection list is cached in your session.
Viraly Trigger not firing on schedule
Check the trigger node’s Poll Times setting. On self-hosted n8n, polling can run as often as every minute. On n8n Cloud, the minimum interval depends on your plan. Verify the workflow is activated (toggle in the top-right of the canvas) and that your n8n Cloud plan hasn’t hit its execution quota.
Create Post action returns 403 Forbidden
The OAuth credential doesn’t have the posts:write scope. In Viraly, go to Settings → Integrations → n8n and check the Granted scopes list. If posts:write is missing, disconnect, then edit the credential in n8n and click Connect my account again, accepting all requested scopes.