Connect Katana to Spike.sh

Both apps 49Katana 24Spike.sh 25

• Trigger
  New Customer

  Triggers when a new customer is created in Katana.

• Trigger
  New Sales Order

  Triggers when a new sales order is created in Katana.

• Action
  Add manufacturing order

  Creates a manufacturing order in Katana for a product variant at a location. Recipe and operation rows are added automatically from the product's recipe.

• Action
  Add material

  Creates a material in Katana, with one or more variants, and returns the new material.

• Action
  Add product

  Creates a product in Katana with one or more variants, including its unit of measure, category, and sell/make/buy settings.

• Action
  Add purchase order

  Creates a purchase order for a supplier, together with its line items, in Katana.

• Action
  Create Customer

  Creates a customer in Katana.

• Action
  Create Sales Order

  Creates a sales order in Katana for a customer with one product variant line.

• Action
  Delete customer

  Deletes a customer from Katana by its ID.

• Action
  Delete sales order

  Deletes a single sales order in Katana by its ID.

• Action
  Find Customer

  Finds Katana customers matching a name, email or phone number.

• Action
  Get manufacturing order

  Returns the details of a manufacturing order, including its status, quantities, costs, dates and custom field values.

• Action
  Get product

  Returns a Katana product by its ID, including its variants and configuration options.

• Action
  Get purchase order

  Returns a purchase order by its ID, including its rows, totals, status and custom field values.

• Action
  Get Sales Order

  Returns one Katana sales order by its ID.

• Action
  List customers

  Returns the customers in your Katana account, most recent first, optionally filtered by name, email, company, category and date ranges.

• Action
  List inventory

  Returns current inventory levels per variant and location, optionally filtered by location or variant.

• Action
  List manufacturing orders

  Returns manufacturing orders, most recent first, optionally filtered by status, order number, location, linked sales order, or created/updated date ranges.

• Action
  List products

  Returns the products in your Katana account, most recent first, optionally filtered by name, unit of measure, flags, supplier or date ranges.

• Action
  List purchase orders

  Returns the purchase orders in your Katana account, most recent first, optionally filtered by status, supplier, location, order number and date ranges.

• Action
  List sales orders

  Returns the sales orders in your Katana account, most recent first, optionally filtered by customer, status, location, dates and more.

• Action
  Update Customer

  Updates an existing Katana customer. Only the fields you fill in are changed.

• Action
  Update product

  Updates an existing Katana product. Only the fields you fill in are changed; everything else is left as it is.

• Action
  Update sales order

  Updates an existing Katana sales order. Only the fields you fill in are changed; everything else is left as is.

• Action
  Acknowledge incident

  Acknowledge one or more Spike.sh incidents by counter id or incident id.

• Action
  Add alert rule

  Create a new alert routing/automation rule with conditions and actions.

• Action
  Add escalation

  Creates a new escalation policy for a Spike.sh team, defining who is notified, through which channel, and how long to wait between steps.

• Action
  Add integration

  Create a new integration for a team (source system that sends alerts into Spike).

• Action
  Add on-call

  Create a new on-call schedule for a team.

• Action
  Add service

  Create a new service in a team, with name and description.

• Action
  Create Incident

  Creates a Spike incident through one of your integrations and sends alerts. The integration decides which service and escalation policy the incident is routed to.

• Action
  Delete alert rule

  Archives (soft-deletes) a Spike alert rule so it no longer applies to incoming incidents.

• Action
  Delete escalation

  Archives (soft-deletes) a Spike escalation policy by its ID.

• Action
  Escalate incident

  Escalates one or more Spike incidents to the next step of their escalation policy.

• Action
  Get escalation

  Get escalation policy details by id.

• Action
  Get incident

  Fetch a single incident by counter id.

• Action
  Get integration

  Fetches an integration by its token, including its name, type, service, escalation settings and webhook URL. An error occurs if the integration is not found.

• Action
  Get service

  Get a Spike service's details, along with its incidents and open-incident count.

• Action
  List alert rules

  Lists all alert rules (enabled and disabled) configured for a Spike team.

• Action
  List escalations

  Lists the escalation policies that belong to a Spike team.

• Action
  List incidents

  Lists the incidents for a Spike.sh team.

• Action
  List on-calls

  Lists the on-call schedules for a team.

• Action
  List services

  Lists the services in a Spike team.

• Action
  List teams

  Lists every team in your Spike organisation. Use a team's ID from here wherever other Spike actions ask for a team.

• Action
  Resolve incident

  Resolve one or more incidents by counter id array.

• Action
  Update alert rule

  Replace an existing Spike alert rule's name, conditions and actions.

• Action
  Update escalation

  Replaces an existing escalation policy's name, steps and start delay. The whole policy is replaced, so send every step you want to keep.

• Action
  Update on-call

  Updates an on-call schedule's name and/or moves it to another team. Rotations and layers are not changed by this action.

• Action
  Update service

  Updates the name and/or description of an existing Spike.sh service.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.