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 Agile CRM 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.
10 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 Agile CRM and one approval.
The scene shows the path of a request; the exact actions depend on the functions your company enables in Agile CRM.
Input
A team member asks, in the conversation, for something that today requires opening Agile CRM — 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 Agile CRM with the person's own credential.
02If the request requires writing something in Agile CRM, 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
Agile CRM 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 Agile CRM; 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
Agile CRM inside the conversation where the work happens.
Three common situations for people who use Agile CRM every day. What Skyller does in each one depends on the functions your company turns on.
Preparing the meeting
“Summarize this customer's history before the call.”
The salesperson asks by name. Skyller queries Agile CRM through the read functions enabled for sales and builds the summary with the latest interactions and the deal stage.
CRM context in the conversation
Logging the follow-up
“Create the follow-up activity for Friday.”
Creating a record in Agile CRM is a write action; with the function set to ask for approval, Skyller shows the card with the deal, the date and the note and waits for Approve.
Record with approval
Administering
“Reading, yes. Changing a proposal's value, no.”
The administrator turns on reading and activity creation for the team; changing values and deleting records stay off. Every call to Agile CRM goes in the record.
Function by function
Actions and events
What the vendor offers in Agile CRM.
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 10 of 10
Create Contact or Company
AGILE_CRM_CREATE_CONTACT_OR_COMPANY
Create a person contact with optional tags and scoring, or a company, with common and tenant custom properties.
Create Deal
AGILE_CRM_CREATE_DEAL
Create a deal, optionally associate contacts, and validate or resolve a case-sensitive milestone from the selected or default pipeline.
Delete Contact or Company
AGILE_CRM_DELETE_CONTACT_OR_COMPANY
Permanently delete one person contact or company by numeric ID.
Delete Deal
AGILE_CRM_DELETE_DEAL
Permanently delete one deal by its numeric Agile CRM ID.
Get Contact or Company
AGILE_CRM_GET_CONTACT_OR_COMPANY
Get one person contact or company by its numeric Agile CRM ID; return null when the resource does not exist.
Get Deal
AGILE_CRM_GET_DEAL
Get one deal by its numeric Agile CRM ID; return null when the deal does not exist.
List Contacts
AGILE_CRM_LIST_CONTACTS
Return one creation-ordered page of person contacts, with a cursor for the next page when more contacts exist.
List Deals
AGILE_CRM_LIST_DEALS
Return one creation-ordered page of deals, with a cursor for the next page when more deals exist.
Update Contact or Company
AGILE_CRM_UPDATE_CONTACT_OR_COMPANY
Add or replace selected properties on one person contact or company without replacing properties that are not included.
Update Deal
AGILE_CRM_UPDATE_DEAL
Partially update selected fields of an existing deal without replacing fields that are not supplied.
Before you start
What your company needs to use Agile CRM.
Login
Each person enters their own Agile CRM API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs
An administrator connects Agile CRM for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
10 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.
Try it free with your team or book a demo: together we pick the Agile CRM functions to enable and show the first approved action, with fictitious data.