Integration
Connect Demio to PocketSmith
When something happens in Demio, 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 Demio 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 Demio and PocketSmith
Triggers and actions 4 triggers ยท 13 actions
Trigger
Does Not Attend WebinarTriggers when a webinar ends and we detect a registrant did not attended.
Trigger
New Webinar RegistrationTriggers when there is a new registration for a webinar.
Trigger
Webinar UpdateTriggers after a webinar has ended. If using a series webinar, we provide the date of the next schedule series.
Action
Get eventReturns information about a specific Event, including a full list of its Event Sessions ordered by scheduled date/time. GET /events/{event_id}
Action
Get event sessionReturns information about a specific Event Session. GET /events/{event_id}/sessions/{date_id}
Action
List event participantsReturns the Event Date participants list, optionally filtered by status query param (attended, did not attend, completed, left early, banned). GET /report/{event_id}/{date_id}/participants
Action
List eventsReturns active (not canceled) Events grouped by Event ID, ordered by next upcoming session date/time. Supports type=upcoming query param to filter to upcoming events only. GET /events
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.