Integration
Connect BlogIn to swiDOC
When New Post fires in BlogIn, your agent runs Update document metadata in swiDOC. 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 BlogIn and swiDOC 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 BlogIn can start in swiDOC
When New Post in BlogIn
then Update document metadata in swiDOC
When New User in BlogIn
then Download document in swiDOC
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 BlogIn and swiDOC
Triggers and actions 4 triggers · 15 actions
Trigger
New PostTriggers when a new post is published on BlogIn.
Trigger
New UserTriggers when a new member joins your BlogIn workspace.
Trigger
Post UpdatedTriggers when a published BlogIn post changes (title, flags, approval or publish date).
Trigger
User UpdatedTriggers when a BlogIn member's profile changes.
Action
Add Post CommentAdds a comment to a BlogIn post.
Action
Create MemberCreates a new member in your BlogIn workspace.
Action
Create New DraftCreates a new post on BlogIn as an unpublished draft.
Action
Create PageCreates a BlogIn page.
Action
Create TeamCreates a BlogIn team.
Action
Delete PostDeletes a BlogIn post.
Action
Get MemberReturns one BlogIn member by id, with their name, email, role and teams.
Action
Get PostReturns one BlogIn post by id, with its title, text, author and publish state.
Action
Publish New PostCreates and publishes a new post on BlogIn.
Action
SearchSearches BlogIn posts by search terms and returns the matching items.
Action
Update PostUpdates a BlogIn post. Only the fields you fill in are changed.
Action
Archive DocumentArchives a file in swiDOC with its name, folder path, description, tags and search attributes, and returns the new document's id.
Action
Download documentDownloads an archived swiDOC document as a file you can pass to later steps.
Action
Get document metadataReturns the metadata of an archived document: its file name, folder path, description, tags, archive dates and search attribute values.
Action
Update document metadataUpdates the metadata of an archived swiDOC document, such as its file name, folder path, description, tags, search attributes or archive duration. Only the values you fill in are changed.
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 BlogIn
BlogIn to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
BlogIn to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
BlogIn to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
BlogIn to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
BlogIn to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
BlogIn to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into swiDOC
HubSpot to swiDOCHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to swiDOCSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to swiDOCSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to swiDOCGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to swiDOCGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to swiDOCGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
BlogIn and swiDOC, answered
What can start an automation from BlogIn?
Any of BlogIn's 4 triggers in the catalog, including New Post, New User, Post Updated and User Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in swiDOC when something happens in BlogIn?
Any of swiDOC's 4 actions, including Update document metadata, Download document, Get document metadata and Archive Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from swiDOC to BlogIn?
swiDOC has no triggers in the catalog today, so automations start in BlogIn. If you need the other direction, ask: your agent reads swiDOC's API documentation and adds it.
Do I have to build a connector for BlogIn or swiDOC?
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 BlogIn and swiDOC 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.