We use necessary features to run the website and platform. With your permission, we also measure usage and performance and use marketing cookies for advertising and remarketing. Your choice applies in this browser across the website, signup and platform. Cookie policy
Closing this notice or pressing Esc lets you continue with necessary features only.
Connect Blooio to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.
Description and action names are the ones the vendor publishes, in English; action descriptions are shown summarized. Skyller does not alter that content.
26 ACTIONS
published by the vendor; the company enables only the necessary ones
0 EVENTS
triggers the system can send, when the vendor offers them
API KEY
each person signs in with their own credential, encrypted
APPROVAL BY RISK
sensitive actions show a card before running
Live proof
One request, one query in Blooio and one approval.
The scene shows the path of a request; the exact actions depend on the functions your company enables in Blooio.
Input
A team member asks, in the conversation, for something that today requires opening Blooio — inside their area's space, with their login.
What Skyller does
01Picks, among the enabled functions, a query action and looks the information up in Blooio with the person's own credential.
02If the request requires writing something in Blooio, acts within permission; if the function is sensitive, it first shows the card and waits for Approve.
03Returns the result in the conversation and records who asked, which action was used and when.
Result
Blooio stops being an open tab and starts answering inside the conversation — through the functions your company enabled.
Good to know
The available actions are the ones the vendor publishes for Blooio; in your company only the functions turned on by the administrator are available.
If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
Being in this catalog does not mean being installed, with a valid login, working in your company.
Illustrative scene with fictitious data; no action is named because the choice depends on the functions your company enables.
Where this helps your work
Blooio inside the conversation where the work happens.
Three common situations for people who use Blooio every day. What Skyller does in each one depends on the functions your company turns on.
Needing to know what was agreed
“What did they decide in the project channel yesterday?”
The person asks and Skyller reads the channel in Blooio with their login, only in the channels they belong to, and summarizes what was agreed.
Channel summary in the conversation
Notifying the team
“Tell the team the new policy has been published.”
Posting a message is a write action; with the function set to ask for approval, Skyller shows the card with channel and text and only sends it in Blooio after Approve.
Message with approval
Administering
“A tool is one thing. A conversation channel is another.”
Here Blooio is a tool: the AI reads and writes in it through the enabled functions. Talking to Skyller from inside Blooio is a channel, contracted separately.
Two things, two controls
Actions and events
What the vendor offers in Blooio.
Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.
Showing 12 of 26
Add Contact Tags
BLOOIO_ADD_CONTACT_TAGS
Add or reactivate one or more free-form tags on a contact.
Create Contact
BLOOIO_CREATE_CONTACT
Create a contact from an E.164 phone number or email address, optionally assigning a name.
Create Group
BLOOIO_CREATE_GROUP
Create a messaging group, optionally linking an existing iMessage chat and recording its members; new contacts may be created for unknown members.
Delete Contact
BLOOIO_DELETE_CONTACT
Soft-delete one contact identified by E.164 phone number or email.
Delete Group
BLOOIO_DELETE_GROUP
Soft-delete a group, remove its members, and exit its linked iMessage chat when one exists.
Get Account
BLOOIO_GET_ACCOUNT
Return the authenticated organization, assigned devices, and message usage without exposing the API-key identifier.
Get Chat
BLOOIO_GET_CHAT
Return detailed counts, participant context, and latest-message metadata for one conversation.
Get Contact
BLOOIO_GET_CONTACT
Return one contact by E.164 phone number or email, including its current tags.
Get Contact Capabilities
BLOOIO_GET_CONTACT_CAPABILITIES
Check whether a contact can receive iMessage, SMS, or FaceTime before choosing a communication path.
Get Group
BLOOIO_GET_GROUP
Return one messaging group by its grp_ identifier.
Get Message
BLOOIO_GET_MESSAGE
Return one message with content, reactions, delivery status, protocol, errors, and inline-reply context.
Get Poll Results
BLOOIO_GET_POLL_RESULTS
Return a poll's definition, option vote counts, and total votes.
Before you start
What your company needs to use Blooio.
Login
Each person enters their own Blooio API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs
An administrator connects Blooio for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
26 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan
Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.