Integration
Connect PocketSmith to Billage
When something happens in PocketSmith, your agent does the next thing in Billage. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want PocketSmith and Billage 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 PocketSmith and Billage
Triggers and actions 1 trigger ยท 25 actions
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}.
Action
Add ProductCreate a new Billage product. POST /v2/products.
Action
Create AccountCreates a new account.
Action
Create ContactCreates a new contact in an account.
Action
Delete AccountDelete a Billage account by id. DELETE /v2/accounts/{account-id}.
Action
Delete ContactDelete a Billage contact by id. DELETE /v2/contacts/{id}.
Action
Delete LeadDelete a Billage lead by id. DELETE /v2/leads/{id}.
Action
Get AccountFetch a single Billage account (company/customer record) by id. GET /v2/accounts/{account-id}.
Action
Get ContactFetch a single Billage contact by id. GET /v2/contacts/{id}.
Action
Get LeadFetch a single Billage lead by id. GET /v2/leads/{id}.
Action
Get ProductFind a Billage product by id. GET /v2/products/{id}.
Action
List AccountsList/search Billage accounts by name, alias, vat, tags, etc. GET /v2/accounts.
Action
List ContactsList/search Billage contacts by criteria. GET /v2/contacts.
Action
List LeadsList Billage leads. GET /v2/leads.
Action
List ProductsList/search Billage products by alias or name. GET /v2/products.
Action
Update AccountUpdate an existing Billage account. PUT /v2/accounts.
Action
Update ContactUpdate an existing Billage contact. PUT /v2/contacts.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.