Integration
Connect Jumpseller to Meisterplan
When something happens in Jumpseller, your agent does the next thing in Meisterplan. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Jumpseller and Meisterplan 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 Jumpseller and Meisterplan
Triggers and actions 6 triggers ยท 36 actions
Trigger
Customer CreatedTriggers when a new customer registers into the store.
Trigger
Customer UpdatedTriggers when a customer is updated.
Trigger
Order PaidTriggers when a new order is paid.
Trigger
Order UpdatedTriggers when an order status is updated (from an initial "pending payment" to either a "paid", "canceled" or "abandoned" status).
Trigger
Product CreatedTriggers when a new product is created.
Trigger
Product UpdatedTriggers when a product is updated.
Action
Add CategoryCreate a new Category. POST /categories.json
Action
Add CustomerAdds a new customer to your Jumpseller store.
Action
Create ProductCreates a Product
Action
Create Product VariantCreates a new Product Variant
Action
Delete CustomerDelete an existing Customer. DELETE /customers/{id}.json
Action
Delete ProductDelete an existing Product. DELETE /products/{id}.json
Action
Find Customer From EmailFinds a customer in your Jumpseller store by their email address.
Action
Find ProductFinds a Jumpseller Product, returning the full product details (including its variants)
Action
Find Product From SKUFinds a product given a SKU, ID or Barcode
Action
Get CustomerRetrieve a single Customer by id. GET /customers/{id}.json
Action
Get ProductRetrieve a single Product by id. GET /products/{id}.json
Action
List CategoriesRetrieve all Categories. GET /categories.json
Action
List CustomersRetrieve all Customers. GET /customers.json
Action
List ProductsRetrieve all Products in the store. GET /products.json (supports category/status filters and pagination).
Action
Update CustomerUpdates an existing customer in your Jumpseller store.
Action
Update ProductUpdates a Product
Action
Update Product by SKUUpdates a product given a SKU
Action
Create or Update Actual Time WorkedRecords the hours a resource or role actually worked on a project for a given date, updating the existing entry if one is already there. Returns the stored entry.
Action
Create or Update AllocationAllocates a resource or role to a project for a date range, updating the existing allocation if one is already there. Returns the allocation with its resulting segments.
Action
Create or Update a Project's Tool LinkLinks a Meisterplan project to the matching project in a task management tool, updating the link if one already exists. Returns the stored link.
Action
Create or Update Resource AbsenceRecords an absence for a resource over a date range, so the time is taken out of their availability. Returns the stored absence.
Action
Create or Update Tasks of a Project's Tool LinkPushes a task from a linked task management tool onto a Meisterplan project, updating it if the task key is already there.
Action
Create ProjectCreates a project in a Meisterplan scenario, including its dates, budgets and custom fields. Returns the new project.
Action
Create ResourceAdds a person to the Meisterplan resource pool, with their role, calendar, cost rate and org placement. Returns the new resource.
Action
Create RoleCreates a role in Meisterplan that resources can be assigned to and projects can be allocated against. Returns the new role.
Action
Find a Resource or RoleReturns the resources and roles whose key, name or email matches the text you supply. Meisterplan has no server-side search on these collections, so the match is made after fetching them.
Action
Find a Team, Resource or RoleReturns the teams, resources and roles whose name, key or email matches the text you supply. Meisterplan has no server-side search on these collections, so the match is made after fetching them.
Action
Find Project by KeyReturns the project in a scenario that carries the project key you supply. Meisterplan has no server-side project search, so the match is made after fetching the scenario's projects.
Action
Find Project by NameReturns the projects in a scenario whose name contains the text you supply. Meisterplan has no server-side project search, so the match is made after fetching the scenario's projects.
Action
Find Resource by EmailReturns the resource whose email address matches the one you supply. Meisterplan has no server-side resource search, so the match is made after fetching the resource pool.
Action
Find Resource by KeyReturns the resource carrying the resource key you supply. Meisterplan has no server-side resource search, so the match is made after fetching the resource pool.
Action
Find Role by NameReturns the role carrying the name you supply. Meisterplan has no server-side role search, so the match is made after fetching the roles.
Action
Find Task by KeyReturns the task on a project's tool link that carries the task key you supply. Meisterplan has no server-side task search, so the match is made after fetching the project's tasks.
Action
Update ProjectUpdates a project in a Meisterplan scenario โ its dates, budgets, status and custom fields. Only the values supplied are changed. Returns the updated project.
Action
Update ResourceUpdates a person in the Meisterplan resource pool โ their name, role, calendar, cost rate and org placement. Only the values supplied are changed. Returns the updated resource.
Action
Update RoleUpdates a role in Meisterplan โ its name, cost rate and org placement. Only the values supplied are changed. Returns the updated role.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.