Integration
Connect DropInBlog and Siteleaf
When Post Published fires in DropInBlog, your agent runs Create Document in Siteleaf, or New Collection in Siteleaf to Find posts by keyword in DropInBlog. Describe the whole flow 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 DropInBlog and Siteleaf to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 DropInBlog and Siteleaf can do together
From DropInBlog to Siteleaf
When Post Published in DropInBlog
then Create Document in Siteleaf
From Siteleaf to DropInBlog
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 DropInBlog and Siteleaf
Triggers and actions 5 triggers · 22 actions
- Post Published
Triggers when a blog post is published on your DropInBlog blog.
- Find posts by keyword
Returns blog posts matching a keyword or phrase, optionally filtered by status.
- Get author
Returns a single blog author's details by its ID.
- Get category
Returns a single blog category by its ID.
- Get post
Returns a single blog post by its ID, including its content, categories and author.
- List posts
Returns the blog's posts, optionally filtered by status, visibility, category, author, specific posts, or publish/modify date range.
- New Collection
Triggered when a new collection is created.
- New Document
Triggered when a new document is created.
- New Page
Triggered when a new page is created.
- New Site
Triggered when a new site is created.
- Add Collection
Create a new collection on a site.
- Create Document
Creates a new document.
- Create Page
Creates a new page.
- Delete Collection
Delete a collection.
- Delete Document
Delete a document.
- Delete Page
Delete a page.
- Get Document
Get a single document by id.
- Get Page
Get a single page by id.
- Get Site
Get a single site by id.
- List Collections
List collections for a site.
- List Documents
List documents in a collection, filterable by search/visibility/extensions.
- List Pages
List pages for a site, filterable by search/visibility/extensions.
- List Sites
List all sites for the authenticated user.
- Update Collection
Update a collection's title/path/metadata.
- Update Document
Update an existing document's title/body/tags/categories/metadata.
- Update Page
Update an existing page's title/body/metadata.
- Update Site
Update 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 DropInBlog
DropInBlog to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DropInBlog to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DropInBlog to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DropInBlog to Google SheetsGoogle Sheets
DropInBlog to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
DropInBlog 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.
Questions
DropInBlog and Siteleaf, answered
What can start an automation from DropInBlog?
Any of DropInBlog's 1 trigger in the catalog, including Post Published. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Siteleaf when something happens in DropInBlog?
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 DropInBlog?
Yes. When something happens in Siteleaf, your agent can act in DropInBlog too. This page covers both directions: Siteleaf's triggers and DropInBlog's actions are listed here as well.
Do I have to build a connector for DropInBlog 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.
Can my AI client use DropInBlog and Siteleaf without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.