Integration
Connect Zendesk to HackMD
When New Messaging Conversation fires in Zendesk, your agent runs Create Note in HackMD. 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 Zendesk and HackMD 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 Zendesk can start in HackMD
When New Messaging Conversation in Zendesk
then Create Note in HackMD
When New Ticket in Zendesk
then Update Note in HackMD
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 Zendesk and HackMD
Triggers and actions 3 triggers · 24 actions
Trigger
New Messaging ConversationTriggers when a customer starts a new conversation through Zendesk messaging (the web widget, mobile SDK or a social messaging channel). Each conversation arrives as its Zendesk ticket.
Trigger
New TicketPolling trigger that fires when a new ticket is created.
Trigger
New UserPolling trigger that fires when a new user is created.
Action
Add Comment to TicketAdds a public or private comment to an existing ticket.
Action
Create OrganizationCreates a new organization.
Action
Create TicketCreates a new ticket in Zendesk.
Action
Create UserCreates a new user (end-user or agent).
Action
Delete TicketDeletes a ticket by ID.
Action
Delete UserSoft-deletes a user by ID.
Action
Get Messaging User IDReturns the Zendesk messaging ID for a user, so their messaging conversation can be looked up in Zendesk Messaging.
Action
Get OrganizationRetrieves a single organization by ID.
Action
Get TicketRetrieves a single ticket by ID.
Action
Get UserRetrieves a single user by ID.
Action
List OrganizationsLists organizations in the account.
Action
List Ticket CommentsLists all comments on a ticket.
Action
List TicketsLists tickets in the account.
Action
SearchRuns a Zendesk search query across tickets, users, and organizations.
Action
Search UsersSearches users by query (name, email, etc.).
Action
Update OrganizationUpdates an existing organization by ID.
Action
Update TicketUpdates an existing ticket by ID.
Action
Update UserUpdates an existing user by ID.
Action
Create NoteCreates a Note on HackMD
Action
Delete NoteDeletes a note from the authenticated user's personal workspace by noteId.
Action
Get My NoteGet a note from HackMD
Action
Get My NotesTriggers when getting all my notes.
Action
Get Note HistoryRetrieves the authenticated user's note read/browsing history.
Action
Update NoteUpdates a Note on HackMD
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 Zendesk
Zendesk to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Zendesk to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Zendesk to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Zendesk to AnthropicAnthropic builds Claude, a family of large language models.
Zendesk to GoHighLevelAll-in-one sales and marketing platform agencies white-label and resell to their clients — contacts...
Zendesk to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
More into HackMD
JIRA to HackMDAtlassian JIRA Cloud — issue tracking and project management.
Jira Software Cloud to HackMDJira Software Cloud is a bug and issue tracking tool that allows software developers to manage product...
HubSpot to HackMDHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to HackMDSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to HackMDSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HackMDGoogle Sheets
Questions
Zendesk and HackMD, answered
What can start an automation from Zendesk?
Any of Zendesk's 3 triggers in the catalog, including New Messaging Conversation, New Ticket and New User. Describe the moment in plain language and your agent picks the right one.
What can your agent do in HackMD when something happens in Zendesk?
Any of HackMD's 6 actions, including Create Note, Update Note, Get My Note and Get My Notes. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from HackMD to Zendesk?
HackMD has no triggers in the catalog today, so automations start in Zendesk. If you need the other direction, ask: your agent reads HackMD's API documentation and adds it.
Do I have to build a connector for Zendesk or HackMD?
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.