Integration
Connect PhishStats and Zendesk
When New phishing record fires in PhishStats, your agent runs Add Comment to Ticket in Zendesk, or New Messaging Conversation in Zendesk to Find phishing records in PhishStats. 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 PhishStats and Zendesk 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 PhishStats and Zendesk can do together
From PhishStats to Zendesk
When New phishing record in PhishStats
then Add Comment to Ticket in Zendesk
When New phishing record in PhishStats
then Create Ticket in Zendesk
From Zendesk to PhishStats
When New Messaging Conversation in Zendesk
then Find phishing records in PhishStats
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 PhishStats and Zendesk
Triggers and actions 4 triggers · 19 actions
Trigger
New phishing recordPolling trigger for newly added phishing URLs.
Action
Find phishing recordsSearch the PhishStats phishing database.
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.
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 PhishStats
PhishStats to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
PhishStats to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
PhishStats to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
PhishStats to StripeStripe is a payment processing platform for online businesses.
PhishStats to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
PhishStats to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Zendesk
HubSpot to ZendeskHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ZendeskSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ZendeskSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ZendeskGoogle Sheets
Gmail to ZendeskGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ZendeskGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
PhishStats and Zendesk, answered
What can start an automation from PhishStats?
Any of PhishStats's 1 trigger in the catalog, including New phishing record. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Zendesk when something happens in PhishStats?
Any of Zendesk's 18 actions, including Create Organization, Create Ticket, Create User and Update Organization. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Zendesk to PhishStats?
Yes. When something happens in Zendesk, your agent can act in PhishStats too. This page covers both directions: Zendesk's triggers and PhishStats's actions are listed here as well.
Do I have to build a connector for PhishStats or Zendesk?
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.