Integration
Connect Customer.guru to PocketSmith
When something happens in Customer.guru, your agent does the next thing in PocketSmith. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Customer.guru and PocketSmith to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Customer.guru and PocketSmith
Triggers and actions 2 triggers · 11 actions
Trigger
New RatingTriggered when a customer submits a new rating on one of your Customer.guru surveys, giving you their score, their comment and how they engaged with the survey email.
- Find Customer
Looks up a customer in your Customer.guru account by email address and returns that customer's record — their id, when they were added, their most recent survey score and comment, and whether they have unsubscribed.
- Schedule Survey
Sends a Customer.guru NPS survey to one or more customers, either straight away or scheduled for a later date, and reports how many went out.
Trigger
New transactionFires when a new transaction appears in the authorised user's PocketSmith accounts. Poll GET /users/{id}/transactions sorted by created/updated date, dedup on transaction id.
- Add category
Create a new category for the authorised user. POST /users/{id}/categories.
- Add transaction
Create a new transaction in a PocketSmith transaction account. POST /transaction_accounts/{id}/transactions.
- Delete category
Delete a category by id. DELETE /categories/{id}.
- Delete transaction
Delete a transaction by id. DELETE /transactions/{id}.
- Get account
Retrieve a single account by id. GET /accounts/{id}.
- Get category
Retrieve a single category by id. GET /categories/{id}.
- Get transaction
Retrieve a single transaction by id. GET /transactions/{id}.
- Update category
Update an existing category's title, colour or parent. PUT /categories/{id}.
- Update transaction
Update fields on an existing transaction (amount, payee, date, category, note, labels). PUT /transactions/{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