Integration
Connect Emma and PocketSmith
When New mailing fires in Emma, your agent runs Add category in PocketSmith, or New transaction in PocketSmith to Get member by email in Emma. 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 Emma and PocketSmith 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 Emma and PocketSmith can do together
From Emma to PocketSmith
When New mailing in Emma
then Add category in PocketSmith
From PocketSmith to Emma
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 Emma and PocketSmith
Triggers and actions 3 triggers · 25 actions
- New mailing
Polling trigger: fires when a new mailing (campaign) is created in the account.
- New subscriber
Polling trigger: fires when a new subscriber (member) is added to the account.
- Delete member
Delete a member by member ID (sets status to deleted).
- Get mailing
Get a single mailing by mailing ID.
- Get mailing members
Get the members a mailing was sent to.
- Get member
Get a single member by member ID.
- Get member by email
Look up a single member by email address.
- List fields
List the member data fields defined in the account.
- List groups
List all member groups in the account.
- List mailings
List mailings (campaigns) in the account.
- List members
List all members (subscribers) in the Emma account.
- List members in group
List the members belonging to a specific group.
- List signup forms
List the signup forms in the account.
- Opt out member
Opt a member out of all mailings by email address.
- New transaction
Fires when a new transaction appears in the authorised user's PocketSmith accounts.
- Add category
Create a new category for the authorised user.
- Add transaction
Create a new transaction in a PocketSmith transaction account.
- Delete category
Delete a category by id.
- Delete transaction
Delete a transaction by id.
- Get account
Retrieve a single account by id.
- Get category
Retrieve a single category by id.
- Get transaction
Retrieve a single transaction by id.
- List accounts
List all bank/investment accounts for the authorised user.
- List categories
List all categories for the authorised user.
- List transaction accounts
List the transaction accounts (e.g. individual bank feeds) belonging to the authorised user, needed as the parent for creating transactions.
- List transactions
List transactions for the authorised user, with filters for date range, category, account, type and search text.
- Update category
Update an existing category's title, colour or parent.
- Update transaction
Update fields on an existing transaction (amount, payee, date, category, note, labels).
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 Emma
Emma to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Emma to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Emma to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Emma to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Emma to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Emma to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into PocketSmith
Google Drive to PocketSmithGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PocketSmithMailchimp marketing automation and email platform.
Questions
Emma and PocketSmith, answered
What can start an automation from Emma?
Any of Emma's 2 triggers in the catalog, including New mailing and New subscriber. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PocketSmith when something happens in Emma?
Any of PocketSmith's 13 actions, including Update category, Update transaction, Add category and Add transaction. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PocketSmith to Emma?
Yes. When something happens in PocketSmith, your agent can act in Emma too. This page covers both directions: PocketSmith's triggers and Emma's actions are listed here as well.
Do I have to build a connector for Emma or PocketSmith?
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 Emma and PocketSmith 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.