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 Botdog 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.
12 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 Botdog and one approval.
The scene shows the path of a request; the exact actions depend on the functions your company enables in Botdog.
Input
A team member asks, in the conversation, for something that today requires opening Botdog — 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 Botdog with the person's own credential.
02If the request requires writing something in Botdog, 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
Botdog 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 Botdog; 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
Botdog inside the conversation where the work happens.
Three common situations for people who use Botdog 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 Botdog 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 Botdog 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 Botdog goes in the record.
Function by function
Actions and events
What the vendor offers in Botdog.
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 12
Add Leads to Campaign
BOTDOG_ADD_LEADS_TO_CAMPAIGN
Create 1 to 100 lead records from LinkedIn profiles in an existing campaign.
Get Analytics
BOTDOG_GET_ANALYTICS
Return outreach analytics for a preset period, either as team/campaign totals or as a per-user breakdown.
Get Campaign
BOTDOG_GET_CAMPAIGN
Return one campaign's identity, status, owner, and configured dates by campaign ID.
Get Campaign Sequence
BOTDOG_GET_CAMPAIGN_SEQUENCE
Return a campaign's configured workflow steps and branches in graph, tree, readable, or combined form; this does not edit or launch the campaign.
Get Campaign Statistics
BOTDOG_GET_CAMPAIGN_STATISTICS
Return invitation, message, profile-visit, and response metrics and rates for one campaign.
Get Current Team
BOTDOG_GET_CURRENT_TEAM
Return the name and user count of the Botdog team authenticated by the connected API key.
Get Daily Analytics
BOTDOG_GET_DAILY_ANALYTICS
Return one outreach-activity row per calendar day plus totals for an explicit date range, optionally filtered by user or campaign.
List LinkedIn Accounts
BOTDOG_LIST_ACCOUNTS
Return connected LinkedIn sending accounts and their connection health for the authenticated Botdog team.
List Campaigns
BOTDOG_LIST_CAMPAIGNS
Return campaigns in the authenticated Botdog team, optionally filtered by status or owner user IDs.
List Leads
BOTDOG_LIST_LEADS
Return one cursor-controlled page of team leads, optionally filtered by campaign, list, campaign state, reply state, unread state, or skip state.
List Team Users
BOTDOG_LIST_USERS
Return Botdog users in the authenticated team so their IDs can be used in campaign and analytics filters.
Send or Schedule Message
BOTDOG_SEND_MESSAGE
Immediately send a LinkedIn message to an existing lead conversation, or schedule delivery when send_at is provided.
Before you start
What your company needs to use Botdog.
Login
Each person enters their own Botdog API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs
An administrator connects Botdog for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
12 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.