Integration
Connect Emailchef to Hippo
When New Contact fires in Emailchef, your agent runs Create Summary of Ticket History in Hippo. 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 Emailchef and Hippo 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 Emailchef can start in Hippo
When New Contact in Emailchef
then Create Summary of Ticket History in Hippo
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 Emailchef and Hippo
Triggers and actions 2 triggers · 32 actions
- Contact Unsubscribed
Triggers when a contact unsubscribes from your list.
- New Contact
Triggers when a new contact is added to your list.
- Add blocking
Add an email to the blocklist.
- Add custom field
Create a custom field in a list.
- Add / Update Contact
Adds a new contact or updates an existing one with the provided data.
- Create New List
Creates a new contact list in your account.
- Delete blocking
Remove an email from the blocklist.
- Delete campaign
Delete a campaign.
- Delete custom field
Delete a custom field.
- Delete list
Delete a list.
- Find Contact in List
Finds an existing contact within a specific list by their email address.
- Get contact
Get a contact by id.
- Get list
Get a list by id.
- Import contacts
Bulk import contacts into a list.
- List blockings
Lists the account's blocked email addresses, each with email, type and added_date.
- List contacts
List contacts.
- List custom fields
List custom fields of a list.
- List lists
List all contact lists.
- Unsubscribe Contact in List
Unsubscribes a contact from a specific list using their Contact ID.
- Update custom field
Update a custom field.
- Update list
Update a list.
- Add custom event
Create a custom event for a user (Automation/Create custom event in Hippo Postman docs): app_secret_key, user_unique_key, event_type, etc.
- Create Conversation
Creates a new conversation in the system
- Create or Update User
Create a new user or update an existing one
- Create Summary of Ticket History
Creates a summary of all notes and comments added in the ticket
- Create Ticket
Creates a new ticket in the system
- Get ticket
Get ticket details by ticket_id. POST to Hippo ticketing API (Ticketing/Get Ticket Details in the Postman docs) with ticket_id, app_secret_key.
- List conversations
Fetch a customer's conversation list (Chat/Fetch customer conversation list): email, app_secret_key, start, limit.
- List messages
Fetch messages and chat details for a channel (Chat/Fetch messages and chat details): channel_id, app_secret_key, start, limit.
- Send Broadcast to Users
Sends broadcast messages through hippo
- Send Message
Sends a message in an existing chat
- Update Due Date of Ticket
Updates due date of an existing ticket
- Update Ticket Priority
Updates the priority of a ticket
- Update Ticket Status
Update status of a ticket
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 Emailchef
Emailchef to Smartsheet via API TokenSmartsheet is a work management and collaboration platform.
Emailchef to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Emailchef to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Emailchef to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Emailchef to Google SheetsGoogle Sheets
Emailchef to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Hippo
Outlign to HippoOutlign is a simple Project Management tool for Creative Teams
Questions
Emailchef and Hippo, answered
What can start an automation from Emailchef?
Any of Emailchef's 2 triggers in the catalog, including New Contact and Contact Unsubscribed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Hippo when something happens in Emailchef?
Any of Hippo's 13 actions, including Create Conversation, Create or Update User, Create Summary of Ticket History and Create Ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hippo to Emailchef?
Hippo has no triggers in the catalog today, so automations start in Emailchef. If you need the other direction, ask: your agent reads Hippo's API documentation and adds it.
Do I have to build a connector for Emailchef or Hippo?
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 Emailchef and Hippo 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.