Integration
Connect Dynosend and Siteleaf
When something happens in Dynosend or Siteleaf, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Dynosend and Siteleaf to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Dynosend and Siteleaf can do together
From Dynosend to Siteleaf
When New Contact in Dynosend
then Add Collection in Siteleaf
When New Contact in Dynosend
then Create Document in Siteleaf
From Siteleaf to Dynosend
When New Collection in Siteleaf
then Add tag to contact in Dynosend
When New Document in Siteleaf
then Create a Contact in Dynosend
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Dynosend and Siteleaf
Triggers and actions 5 triggers · 29 actions
Trigger
New ContactTriggers when a new contact is added to your audience.
Action
Add tag to contactAdd a tag to a contact.
Action
Blacklist a ContactAdd a contact to the blacklist
Action
Create a ContactAdd a contact to an audience
Action
Delete a ContactDelete a contact from an audience
Action
Get audienceGet an audience by id.
Action
Get ContactGet one contact from an audience by contact_uid (or email)
Action
List audiencesList audiences.
Action
List contactsList contacts.
Action
Send an EventPerform an event for a specific contact
Action
Subscribe contactSubscribe a contact.
Action
Unsubscribe contactUnsubscribe a contact.
Action
Update contactUpdate a contact.
Trigger
New CollectionTriggered when a new collection is created.
Trigger
New DocumentTriggered when a new document is created.
Trigger
New PageTriggered when a new page is created.
Trigger
New SiteTriggered when a new site is created.
Action
Add CollectionCreate a new collection on a site.
Action
Create DocumentCreates a new document.
Action
Create PageCreates a new page.
Action
Delete CollectionDelete a collection.
Action
Delete DocumentDelete a document.
Action
Delete PageDelete a page.
Action
Get DocumentGet a single document by id.
Action
Get PageGet a single page by id.
Action
Get SiteGet a single site by id.
Action
List CollectionsList collections for a site.
Action
List DocumentsList documents in a collection, filterable by search/visibility/extensions.
Action
List PagesList pages for a site, filterable by search/visibility/extensions.
Action
List SitesList all sites for the authenticated user.
Action
Update CollectionUpdate a collection's title/path/metadata.
Action
Update DocumentUpdate an existing document's title/body/tags/categories/metadata.
Action
Update PageUpdate an existing page's title/body/metadata.
Action
Update SiteUpdate a site's settings.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Dynosend
Dynosend to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Dynosend to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Dynosend to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Dynosend to Google SheetsGoogle Sheets
Dynosend to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Dynosend to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Siteleaf
Shopify to SiteleafShopify is a commerce platform for online stores and retail point-of-sale.
HubSpot to SiteleafHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SiteleafSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SiteleafGoogle Sheets
Gmail to SiteleafGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SiteleafGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Dynosend and Siteleaf, answered
What can start an automation from Dynosend?
Any of Dynosend's 1 trigger in the catalog, including New Contact. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Siteleaf when something happens in Dynosend?
Any of Siteleaf's 17 actions, including Create Document, Create Page, Update Collection and Update Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Siteleaf to Dynosend?
Yes. When something happens in Siteleaf, your agent can act in Dynosend too. This page covers both directions: Siteleaf's triggers and Dynosend's actions are listed here as well.
Do I have to build a connector for Dynosend or Siteleaf?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.