Who can connect AimTell for the company?

A company connection is installed by an administrator.

Can I connect AimTell just for myself?

Anyone can install a personal connection within the plan’s limit and use it in their own conversations.

Do I use my AimTell account or a company account?

Yours: AimTell requires an API key, and each person registers their own, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.

Does Skyller do everything on that action list?

The list is what the vendor offers. What the AI uses in your company is what the administrator turned on, for the groups they defined — Skyller never widens the connector's access.

Does an action in AimTell happen without anyone approving it?

Reads happen within permission. Write actions have a risk level; sensitive ones show a confirmation card before running and are recorded. The company adjusts the classification when needed.

AimTell does not show up in my company's catalog.

The administrator may have hidden the integration for your company, or the vendor may have discontinued it — in that case it leaves the catalog on the next synchronization, without deleting what was already connected. Talk to whoever administers Skyller in your company.

Integration · Communication and chat

AimTell in Skyller.

Connect AimTell 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.

Try it free Book a demo

Actions and events

AimTell

Communication and chat

AimTell is a web push notification platform for managing websites, subscribers, campaigns, segments, and delivery analytics.

Actions: 15
Events: 0

Source: Composio catalog
Login: API key
Country: Global — no specific country
Actions list: re-read from the vendor every 24 hours
Official site: aimtell.com

Description and action names are the ones the vendor publishes, in English; action descriptions are shown summarized. Skyller does not alter that content.

15 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 AimTell and one approval.

The scene shows the path of a request; the exact actions depend on the functions your company enables in AimTell.

Input
A team member asks, in the conversation, for something that today requires opening AimTell — inside their area's space, with their login.
What Skyller does
1. 01Picks, among the enabled functions, a query action and looks the information up in AimTell with the person's own credential.
2. 02If the request requires writing something in AimTell, shows the card with what it is about to do and waits for Approve.
3. 03Returns the result in the conversation and records who asked, which action was used and when.
Result
AimTell stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

What this scene does not promise

The available actions are the ones the vendor publishes for AimTell; 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

AimTell inside the conversation where the work happens.

Three common situations for people who use AimTell 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 AimTell 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: Skyller shows the card with channel and text and only sends it in AimTell after Approve.

Message with approval

Administering

“A tool is one thing. A conversation channel is another.”

Here AimTell is a tool: the AI reads and writes in it through the enabled functions. Talking to Skyller from inside AimTell is a channel, contracted separately.

Two things, two controls

Actions and events

What the vendor offers in AimTell.

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 15

Create Manual Campaign
AIMTELL_CREATE_MANUAL_CAMPAIGN
Create a manual push campaign as a draft only; this tool never schedules or sends it.
Create Segment
AIMTELL_CREATE_SEGMENT
Create a named audience segment for a website from an AimTell segment definition.
Delete Manual Campaign
AIMTELL_DELETE_MANUAL_CAMPAIGN
Permanently delete one manual campaign by ID. This destructive action cannot be undone and permanently removes the campaign.
Delete Segment
AIMTELL_DELETE_SEGMENT
Permanently delete one audience segment by ID. This destructive action cannot be undone; it removes the segment but does not delete its subscribers.
Get Analytics Over Time
AIMTELL_GET_ANALYTICS_OVER_TIME
Return a daily AimTell metric over a date range for all websites or one website.
Get Campaign Results
AIMTELL_GET_CAMPAIGN_RESULTS
Return daily send, delivery, bounce, click, conversion, and available revenue results for a manual, event-triggered, RSS, or welcome campaign.
List Campaigns
AIMTELL_LIST_CAMPAIGNS
Return one page of manual, event-triggered, RSS, or API push campaigns for an AimTell website.
List Notification Logs
AIMTELL_LIST_NOTIFICATION_LOGS
Return one page from AimTell's sampled notification log for the last seven days, optionally filtered to one subscriber.
List Segments
AIMTELL_LIST_SEGMENTS
Return all audience segments for an AimTell website, including the IDs and definitions used for subscriber filtering and campaign targeting.
List Subscribers
AIMTELL_LIST_SUBSCRIBERS
Return one page of subscribers for an AimTell website, optionally filtered by segment or subscriber ID and optionally including attributes or notification history.
List Websites
AIMTELL_LIST_WEBSITES
Return one page of websites available to the connected AimTell account, including site IDs needed by other tools. Use next_cursor to retrieve later pages.
Send Push Notification
AIMTELL_SEND_PUSH_NOTIFICATION
Immediately send a one-off push notification to exactly one explicitly selected audience: subscriber IDs, one segment, one alias, or the website's full reachable audience.

Before you start

What your company needs to use AimTell.

Login: Each person enters their own AimTell API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs: An administrator connects AimTell for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions: 15 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.

Questions from the people who decide