Integration
Connect Jumpseller to QuintaDB
When something happens in Jumpseller, your agent does the next thing in QuintaDB. 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 QuintaDB 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 QuintaDB
Triggers and actions 13 triggers ยท 27 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
Trigger
New DatabaseTriggers when a new database is created in the connected QuintaDB account.
Trigger
New FormTriggers when a new form is added to a QuintaDB database.
Trigger
New Form FieldTriggers when a new field is added to a QuintaDB form.
Trigger
New or Updated RecordTriggers when a record in a QuintaDB form is added or changed.
Trigger
New RecordTriggers when a new record is added to a QuintaDB form.
Trigger
New Table RecordTriggers when a new record is added to a QuintaDB form.
Trigger
New Table ReportTriggers when a new report is created on a QuintaDB form.
Action
Add formAdds a new form (table) to a QuintaDB database. Returns the created form.
Action
Create RecordAdds a new record to a QuintaDB form. The form's own fields are offered for mapping, and the created record's id is returned.
Action
Delete formDeletes a form (table) and its records from a QuintaDB database.
Action
Delete RecordDeletes a record from a QuintaDB form.
Action
Delete recordsDeletes several records from a QuintaDB form in one call.
Action
Find RecordsReturns the records in a QuintaDB form that match the conditions you specify.
Action
Get recordReturns one record from a QuintaDB form, including all of its field values.
Action
Update CellChanges the value of one field on one QuintaDB record.
Action
Update RecordChanges field values on an existing QuintaDB record. Fields you leave blank keep their current value.
Action
Upload fileUploads a file into a file field on an existing QuintaDB record.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.