Integration
Connect DynaPictures to PocketSmith
When something happens in DynaPictures, 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 DynaPictures 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 DynaPictures and PocketSmith
Triggers and actions 4 triggers ยท 11 actions
Trigger
New ImageTriggers when a new image is generated from a template.
- New Template
Triggers when a new design template is created in DynaPictures, delivering its name, thumbnail and layers.
- New Template With Layer Params
Triggers when a new design template is created in DynaPictures, delivering the template together with every layer you can supply values for when generating an image.
- List assets
Returns the images stored in a DynaPictures workspace media library, each with its hosted link, filename and size.
- List templates
Returns every DynaPictures design template in the account, each with its name, thumbnail and customizable layers.
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.