It runs on your own server: work files and records are stored on your infrastructure; content processed by AI goes to the model provider you choose, and data sent to external tools goes to the connections you set up.
Chat · marketing
demo data
Every Monday, draft the week’s posts for LinkedIn, X and Instagram. Nothing goes out until I approve it.
09:14
Remyral09:14
I prepared a workflow draft from the weekly content calendar template. Open it in the editor to match the fields to your scheduling tool.
Workflow draftValid
Weekly content calendar
Trigger
Mon 08:00
Channels
LinkedIn · X · Instagram
Approval
operator
Out
api.scheduler-example.com
Approval · Mon 08:03Awaiting approvalApproved
Week 44 · 15 post drafts
Mon · LinkedIn · New release announcement
Tue · X · A short answer to a customer question
Wed · Instagram · A day with the team
Workflow resultCompleted
15 posts scheduled
Publishing
from the account you connected
Report
sent by email
01Workflowfrom the chat or the editor
Weeklycontentcalendar
It starts from a ready template: an AI step writes the drafts, the team approves, approved posts go to your scheduling tool. You change every node in the editor to fit your own setup.
Workflow · Weekly content calendar
demo data
Weekly content calendarSavedSaveRun
Last run · Mon 08:00 · 7/7 steps completed
02Setup and flowSocial media
Setup and flow
A marketing team or agency posting regularly on several channels.
Setup
Project type
A workspace project (no repository needed); it starts from the ready “Weekly content calendar” workflow template.
Workflow engine
Workflow engine 2 switched on (Settings → Server settings); at least one worker online that runs HTTP and email steps.
Brand voice
Tone, words to avoid and brand facts go into memory as rules or facts; or add them as a skill.
Accounts
The API key of your scheduling tool or platform in the vault, bound to an allowed address; an SMTP account for the report.
What a day looks like
01
On Monday morning the workflow starts on its own; an AI step drafts one post per channel for each weekday for LinkedIn, X and Instagram, in the tone kept in memory and within each channel’s length limit.
02
The drafts wait at an approval step; an authorised team member reads them and approves or rejects. A rejection goes to the person who set up the workflow as a notification.
03
Each approved post goes to your tool’s API with its publish time; the result report arrives by email.
What changes
The weekly drafting does itself and the decision to publish stays with you: no post goes out without approval, and publishing happens through the account you connected.
How it connects
Instead of a ready-made connector, you connect to the API of your scheduling tool or platform with workflows and automations. The template comes with a generic JSON request; you set the fields in the editor to fit your own setup.
We don’t impose a ready-made flow; design your own, either with AI (describe it in the chat) or yourself (in the workflow editor).
Good to know
Extra work such as drafting replies to comments or messages is built from the same parts as a separate flow, as far as the platform’s API allows.
Every platform has its own automation rules; you shape your flow to follow them.
Workflow editor
demo data
A screen from the console · The real console: the workflow editor, with AI steps, conditions and approval on one canvas.
This example runs on the same infrastructure as all the others: Remyral on your own server, and we build your flow together in the pilot. Just describe the work you want to simplify and the tools you use in your application.
Remyral09:14
