Skills
Real capabilities, with guided forms — never raw JSON.
Skills are what your agent can actually do: book the job, log the lead, transfer the emergency, notify the team. Each one is a short, friendly form — which means the owner can wire real work into the agent without an engineer in the room.
Free credits. No credit card. Zero balance pauses — never bills.
Scripted demo — a replay of the real product, not a live session.
The catalog
Everything a good front desk does, as Skills.
Mix and match per agent. The same Skills answer on your phone number and in your website chat — configure once, live on both.
Book on a calendar
Take appointments straight onto a Google Calendar — the caller leaves with a time, not a promise of a callback.
Log to a spreadsheet
Write every lead or request into a Google Sheets row — time, name, number, and what they asked for.
Transfer the call
Warm-transfer to a human with the context handed over — which means nobody repeats their story twice.
Send an email
Notify your team the moment a call needs them: caller name, callback number, and the reason.
Send a text
SMS notifications for the moments email is too slow — an after-hours emergency, a hot lead, a booked job.
Answer from knowledge
Ground answers in your FAQs, docs, and site — so the agent answers from your content, not guesses.
Take a message
When a human isn’t needed right now: capture name, number, and reason, and route it to the right inbox.
Look up a record
Check a status, order, or reference by phone number or ID and read the caller the answer.
Wondering when to hand a call to a human with context versus routing it straight through? Read warm transfer vs cold transfer.
Guided forms
Two fields, not a config file.
This is the entire setup for calendar booking: pick the calendar, set the appointment length. The form asks for what it needs in your language and nothing more — which means adding a capability takes about as long as reading this paragraph.
And every Skill declares its data up front. Before you save it — long before a caller reaches it — you know exactly what it will send, and where.
Book on a calendar
Calendar
Google Calendar — Dispatch
Appointment length
60 minutes
Data that leaves
caller name, phone, requested time → Google Calendar
A recreation of the real Skill form — simplified for the page, true to the product.
Connect your own database
Answers from your own data — on the call.
Connect your own Postgres or MySQL and the agent looks up live records mid-call — an order status, an account balance, the caller's next appointment — and reads the answer back. Every other platform makes you build and host a tool server for this. Flowyte makes it a guided form.
And the safety story is the story. You connect a least-privilege user — never admin credentials — scope the exact tables and columns the agent may see, and freeze every query you approve. Nothing runs that you didn't author.
Connect a SQL database
- 1
Generate a least-privilege user
Flowyte returns the SQL to create a scoped, read-only database user — the agent never uses your admin credentials.
- 2
Discover and scope the schema
Introspect the database, then block any table or column the agent must never see. Scoped-out data disappears from view and is refused at bind time.
- 3
Bind the queries you want as Skills
Map an exact read — or a scoped write — onto a Skill. It freezes to a parameterized statement the agent calls; it never sees raw SQL or the full schema.
- 4
Reads by default, writes gated
Reads run read-only. A write is single-row and lands disabled until you review and publish it — nothing changes your data without your sign-off.
Postgres and MySQL, connected with a guided form — no tool server to build or host.
Know what leaves your system.
See exactly what caller data each Skill sends out — before it ever goes live. It's printed on the Skill while you configure it, and listed again in the pre-publish report's "Data that leaves" section: Book appointment → Google Calendar: name, phone, time. Most platforms make you trust; Flowyte lets you check.
Pair it with Guardrails for what the agent may say, and the pre-publish report for the full pre-flight review — will say, won't say, and what data goes where.
Integrations
Google Calendar and Google Sheets, built in. Everything else, connected.
One org-level connection backs every Skill that uses it — link your calendar once, and any agent can book on it. For the rest of your stack, Skills connect through secure OAuth, webhooks, and the API — the same /api/v1 the dashboard uses — which means no waiting for a connector marketplace to catch up to your tools.
Tutorial: give your agent SkillsPlaybooks: run Skills as one procedure
FAQ
Frequently asked questions
What are Skills in Flowyte?
Do I have to write JSON or code to configure a Skill?
Which integrations does Flowyte support?
How do I know what data a Skill shares?
Can the agent hand a call to a real person?
Can developers build custom Skills?
Hear a Skill do the work.
Call a demo line and ask to book an appointment — that's a calendar Skill answering. Then build your own agent in the studio.
Free credits. No credit card. Zero balance pauses — never bills.
You're calling a real Flowyte agent. Standard rates apply.