Connect Viraly to Make (formerly Integromat) to build advanced multi-step automation scenarios with a visual workflow builder. Trigger scenarios on Viraly events, or create, update, and publish posts from any of Make’s 2,000+ connected apps. This guide walks you through setting up the connection, managing it from within Viraly, and exploring the available modules.
Overview
Make (previously called Integromat) is a visual workflow automation platform similar to Zapier, but geared toward more advanced use cases. It supports branching logic, data transformation, aggregators, iterators, and deeply nested flows — all built in a visual canvas.
The Viraly integration gives Make full access to your workflow: poll for new posts, create and schedule content from any source, look up channels and posts, and receive new bio link subscribers as scenario triggers.
How the setup works: unlike Slack, Discord, or Microsoft Teams (where you start setup inside Viraly), Make connections are created inside Make. When you add a Viraly module to a Make scenario and click “Add connection”, Make redirects you to a Viraly consent screen where you approve the permissions. From that point, Make stores the access token on its side and handles token refresh automatically.
Once connected, you can view the connection status, see what permissions were granted, and revoke access at any time from the Make integration page inside Viraly (Settings → Integrations → Make).
Prerequisites
- A Viraly workspace on the Business plan or higher
- A Make account (free or paid)
- Workspace Owner or Admin role (to authorize the connection)
Connecting Viraly to Make
Setup happens in Make, not in Viraly. Follow these steps:
- Sign in to Make
- Create a new scenario and search for Viraly
- Drag a Viraly module (trigger, action, or search) into the canvas
- Click the module and then Add connection
- Give the connection a name, then click Save
- A Viraly consent window opens. Sign in if needed, pick your workspace, and click Allow Access
- The connection is ready to use across all your scenarios
Make uses OAuth 2.0 with automatic token refresh, so you’ll never need to reconnect as long as the connection stays authorized.
Tip: If you’d rather start from Viraly, go to Settings → Integrations → Make and click Set up in Make. That button opens Make with Viraly pre-filtered in the search results — you still complete setup on Make’s side, but the jumping-off point is inside Viraly.
Managing the Connection in Viraly
After you’ve connected, go to Settings → Integrations → Make inside Viraly. You’ll see:
- Active status — confirms Make has a valid access token for your workspace
- Connected date — when the connection was first authorized
- Last used — when Make most recently called the Viraly API
- Granted scopes — the exact permissions you approved (for example
posts:write,channels:read) - Manage scenarios in Make — jumps back to Make.com
- Disconnect — revokes all Make 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 start a scenario when a matching event happens in Viraly. Make polls Viraly at the interval you configure on the scenario (as frequently as every 15 minutes on the free plan, or once per minute on paid plans).
- 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
- New Bio Link Subscriber — someone subscribed via a Viraly bio link page
Available Actions
- Create Post — schedule, draft, or immediately publish a post
- Update Post — modify an existing scheduled or draft post
- Publish Post Now — force-publish immediately, bypassing the scheduled time
- Delete Post — remove a post that hasn’t been published yet
Available Searches
- Find Post — retrieve a post by its ID
- Find Channel — look up a channel by name or platform
- List Posts — return posts matching your filter criteria
Example Scenarios
- Conditional re-post: Post Published → Router → if channel = Instagram, create a matching post in LinkedIn with adapted caption
- Digest failures: Post Failed → Aggregator (collect hourly) → Email digest to team lead
- Sync new subscribers to multiple destinations: New Bio Link Subscriber → Router → Mailchimp, Klaviyo, Airtable simultaneously
- Batch content from Airtable: Airtable Watch Records → Iterator → Viraly Create Post (schedule each row at staggered times)
Disconnecting
You can revoke Make’s access to your Viraly workspace from inside Viraly — you don’t need to go to Make.com to do it.
- In Viraly, go to Settings → Integrations → Make
- Click Disconnect in the status card
- Confirm in the dialog
Revocation is immediate. Any active scenarios using the connection will start failing with authentication errors on their next run. Make will show a connection error badge on affected scenarios; you can reconnect by going back to any Viraly module in Make and re-adding the connection.
The Settings → Connected Apps page also has a Revoke button that does the same thing.
Troubleshooting
“Authentication failed” on connection
This typically means the OAuth flow was interrupted. Delete the half-created connection in Make and try again from scratch.
I see “Make is not connected yet” in Viraly, but I already set it up
Make sure you completed the full consent flow. If the browser window closed before you clicked Allow Access, no token was issued — go back to Make and re-open the module’s connection dialog to try again.
If the Make integration page still shows “Not connected” after a successful setup, refresh the browser — the connection list is cached in your session.
Scenarios not running on schedule
Check the scenario’s schedule settings in Make. On free plans, the minimum polling interval is 15 minutes. Verify the scenario is toggled on and hasn’t hit your Make operations quota.
Create Post action returns 403 Forbidden
The OAuth connection doesn’t have the posts:write scope. In Viraly, go to Settings → Integrations → Make and check the Granted scopes list. If posts:write is missing, disconnect, then edit the connection in Make and reauthorize, accepting all requested scopes.