Integration
Connect Jumpseller to Snitcher
When something happens in Jumpseller, your agent does the next thing in Snitcher. 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 Snitcher 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 Snitcher
Triggers and actions 8 triggers ยท 28 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 OrganisationTriggered when a new company is identified visiting your website in the selected Snitcher workspace.
Trigger
Organisation Enters SegmentTriggered when a company first appears in the selected Snitcher segment.
Action
Create Custom FieldCreates a new custom field definition on organisations in a Snitcher workspace.
Action
Create TagCreates a new tag in a Snitcher workspace so it can be applied to organisations.
Action
Find ContactsReturns the known contacts at an organisation in Snitcher, looked up by organisation UUID or company domain.
Action
Find OrganisationLooks up an organisation in a Snitcher workspace by company name and returns the first match.
Action
Get User ProfileReturns the name, email and id of the Snitcher user the connection belongs to.
Action
List Custom FieldsReturns all custom field definitions set up on organisations in a Snitcher workspace.
Action
List SegmentsReturns all segments defined in a Snitcher workspace.
Action
List SessionsReturns the website visits (sessions) recorded across a Snitcher workspace for a date or date range, with optional segment, URL and referrer filters.
Action
List WorkspacesReturns the Snitcher workspaces the connected account can access, including each workspace's UUID, name, website and available tags.
Action
Reveal Contact EmailUses a Snitcher email-reveal credit to return the email address of a known organisation contact.
Action
Search OrganisationsSearches the organisations in a Snitcher workspace using advanced field filters.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.