Integration
Connect Basin to PocketSmith
When something happens in Basin, 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 Basin 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 Basin and PocketSmith
Triggers and actions 2 triggers ยท 20 actions
Trigger
New SubmissionTriggers when your form receives a submission.
Action
Add formCreate a new form under a project. POST /api/v1/forms.
Action
Add projectCreate a new project (form-organizing container). POST /api/v1/projects.
Action
Delete formDestroy a form. DELETE /api/v1/forms/:id.
Action
Delete submissionDestroy a submission. DELETE /api/v1/submissions/:id.
Action
Get formRetrieve a single form by id. GET /api/v1/forms/:id.
Action
Get submissionRetrieve a single submission by id. GET /api/v1/submissions/:id.
Action
List formsList all forms accessible to the account. GET /api/v1/forms.
Action
List projectsList all projects accessible to the account. GET /api/v1/projects.
Action
List submissionsList submissions for a form. GET /api/v1/submissions.
Action
Update formUpdate a form's configuration (notifications, spam protection, branding, etc). PATCH/PUT /api/v1/forms/:id.
Action
Update submissionUpdate a submission's state fields (spam, read, trash). PATCH/PUT /api/v1/submissions/:id.
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.
Action
Add categoryCreate a new category for the authorised user. POST /users/{id}/categories.
Action
Add transactionCreate a new transaction in a PocketSmith transaction account. POST /transaction_accounts/{id}/transactions.
Action
Delete categoryDelete a category by id. DELETE /categories/{id}.
Action
Delete transactionDelete a transaction by id. DELETE /transactions/{id}.
Action
Get accountRetrieve a single account by id. GET /accounts/{id}.
Action
Get categoryRetrieve a single category by id. GET /categories/{id}.
Action
Get transactionRetrieve a single transaction by id. GET /transactions/{id}.
Action
Update categoryUpdate an existing category's title, colour or parent. PUT /categories/{id}.
Action
Update transactionUpdate 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.