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 Dynosend 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.
Dynosend is an email marketing platform for managing audiences and contacts, operating campaigns, sending transactional messages, and tracking customer events.
Description and action names are the ones the vendor publishes, in English; action descriptions are shown summarized. Skyller does not alter that content.
18 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 Dynosend and one approval.
The scene shows the path of a request; the exact actions depend on the functions your company enables in Dynosend.
Input
A team member asks, in the conversation, for something that today requires opening Dynosend — 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 Dynosend with the person's own credential.
02If the request requires writing something in Dynosend, 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
Dynosend 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 Dynosend; 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
Dynosend inside the conversation where the work happens.
Three common situations for people who use Dynosend every day. What Skyller does in each one depends on the functions your company turns on.
Answering customers
“What did the customer ask for in the last email?”
The person asks in the conversation and Skyller searches their mailbox in Dynosend, with their login, and summarizes that customer's latest message.
Email summarized without switching tabs
Needing to send
“Send the confirmation to the supplier.”
Sending is a sensitive action: Skyller shows the card with recipient, subject and text and only sends through Dynosend after Approve.
Sending with approval
Administering
“Everyone reads their own mailbox. Nobody reads someone else's.”
The Dynosend connection uses each person's account; the administrator turns on only the functions the routine requires and sees the record of every send.
Own account, a record per send
Actions and events
What the vendor offers in Dynosend.
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 18
Add Email To Blacklist
DYNOSEND_ADD_EMAIL_TO_BLACKLIST
Permanently add an email address to the Dynosend blacklist. This cannot be undone through the Dynosend API because Dynosend exposes no removal operation.
Add Tags To Contact
DYNOSEND_ADD_TAGS_TO_CONTACT
Append one or more tags to a contact without replacing its existing tags.
Check Blacklist
DYNOSEND_CHECK_BLACKLIST
Check whether an email address is on the connected Dynosend account's blacklist and return its timestamp and reason when available.
Create Contact
DYNOSEND_CREATE_CONTACT
Create a contact in an audience, optionally assigning tags and audience-defined custom fields. Can bypass double opt-in when explicitly requested.
Delete Contact
DYNOSEND_DELETE_CONTACT
Permanently delete one contact from an audience for GDPR/CCPA erasure. This destructive operation cannot be undone.
Find Duplicate Contacts
DYNOSEND_FIND_DUPLICATE_CONTACTS
Find contacts that use the same email address across all audiences in the connected Dynosend account.
Get Audience
DYNOSEND_GET_AUDIENCE
Get one audience's configuration, custom-field definitions, contact information, and subscription statistics by audience UID.
Get Campaign
DYNOSEND_GET_CAMPAIGN
Get one campaign's configuration and delivery, open, click, spam, bounce, and unsubscribe insights.
Get Contact
DYNOSEND_GET_CONTACT
Get one contact in an audience by contact UID or email address.
List Audiences
DYNOSEND_LIST_AUDIENCES
List audiences available to the connected Dynosend account, including the UID needed by audience and contact tools.
List Campaigns
DYNOSEND_LIST_CAMPAIGNS
List campaigns in the connected Dynosend account, including status and the campaign UID used by campaign tools.
List Contacts
DYNOSEND_LIST_CONTACTS
Return one page of contacts in a Dynosend audience, including contact UIDs, subscription status, tags, and audience-defined custom-field values.
Before you start
What your company needs to use Dynosend.
Login
Each person enters their own Dynosend API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs
An administrator connects Dynosend for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
18 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.