Tell it
Add the way your business works.
Give Joyflow your services, tone, policies, and common jobs. It starts with your rules instead of guessing.
How work gets done
Flow is the path Joyflow follows after you ask for work. It checks the right places, prepares the next step, and stops when it needs your okay.
Example flow
How it works
You choose what Joyflow can use, see what it prepares, and approve anything that could affect customers, money, or important records.
Tell it
Give Joyflow your services, tone, policies, and common jobs. It starts with your rules instead of guessing.
Limit it
Turn on the apps Joyflow may use for each channel. If an app is off, that work stays off limits.
Ask it
Say what you want done. Joyflow looks things up, prepares the work, and shows the steps as it goes.
Approve it
Emails, refunds, charges, and important record changes wait for your okay before they happen.
Set it up once
Add your services, voice, policies, and documents so replies sound right.
Pick which apps each channel can use. Everything else stays off limits.
Ask in plain language, or run a saved skill when the same job comes back.
Messages, refunds, and bigger changes wait for your sign-off.
Examples
Ask: Send the team a weekly revenue update.
Result: Joyflow checks the numbers, writes the recap, and prepares the file.
Ask: Follow up with this account before Friday.
Result: Joyflow checks the account history, writes the email, and waits before sending.
Ask: Handle this refund if it matches our rules.
Result: Joyflow checks your refund rules, prepares the refund, and asks for approval.
Execution path
A workspace or channel receives the request.
The agent sees business context, channel instructions, enabled connectors, and saved skills.
A proposed tool call is validated against the registered tool schema.
The executor checks permissions, policy gates, risk level, and approval requirements.
Allowed read actions run immediately; sensitive writes wait in Approvals.
The completed action, approval decision, or rejection is logged for review.
FAQ
Joyflow reads the channel context, chooses eligible registered tools, validates the proposed tool call, checks workspace policy, requests approval when needed, and records the outcome.
A saved skill is a reusable SKILL.md-style workflow that captures the steps and constraints for repeat work. It can be run manually, scheduled, or invoked from chat with a slash command.
No. Each channel can limit which connectors and tools are available. If a connector is not enabled for the channel, the agent cannot use it for that lane of work.