Setup Killswitch with Zapier

Easily integrate Killswitch with your backend invoicing systems and hundreds of other applications.

Integrate EV Charger OCPP system with Zapier

You can now integrate Killswitch with the Zapier to create automations and integrate Killswitch with other softwares and platforms.

Zapier is an online integration application that helps you connect different apps and sync actions between them. The Zapier integration for Killswitch enables you to connect and extract order-related information such as order quantity, prices, customer information, payment status, start and end times and other. You can then use this information to integrate with other applications and help you automate workflows and increase productivity with ease.

Using Zapier for Killswitch, you are able to design as many workflows as needed to streamline your operations and business processes. Examples of automations include:

  • Create a new invoice in your ERP system whenever a new Killswitch order is Paid
  • Automatically send an email to a User for every order created
  • Receive an alert whenever there is a Payment error
  • Create a new customer in your CRM system once a new Killswitch Order is created
  • ...and much more!

The Zapier framework

Zapier is an online automation tool that connects your apps and services. You can connect two or more apps to automate repetitive tasks without coding or relying on developers to build the integration. In this context, Killswitch will be an App available in Zapier for you to use in your workflow automations and integrations.

Components of a Zapier framework:

  • Zap: A link between two apps.
  • Trigger: An event that starts a Zap. For example, if you want to create an invoice each time you have a new order Paid, the trigger is a new order with status Paid in Killswitch. In the image below, Killswitch would be "X App".
  • Action: An event that completes a Zap. For example, if you want to create an invoice each time you have a new order Paid, the action is to integrate with your ERP application. In the image below, your ERP Application would be "Y App"
  • Multi Step Zap (Search): A single-step Zap has one trigger and one action. If the Zap has more than one action or includes filters or searches, it is considered a multi-step Zap. I.e. you might want to have 2 actions from a single trigger: create an invoice and send an email message to your customer with the invoice link.
Zapier framework simple schema

Zapier for Killswitch

The Zapier integration for Killswitch Can be found in this link.

To start using Zapier integrations with Killswitch, follow the steps described below.

Killswitch generate API Key
Step 1

Get your Killswitch API Key

check Account settings > Additional info

From the Account management area, expand the "Additional info" section and use the "refresh" sync button to generate a new API Key.

This API Key will be unique to your Account and it will allow Zapier to identify your Killswitch Account when querying for new Orders.

Step 2

Create a new Zap

You can setup Killswitch as a Trigger in your Zapier automations and workflows.

A trigger is an event that starts a Zap. For example, a order Paid in Killswitch triggers a new Invoice in your ERP system.

check Start a new workflow on Zapier

Login to your Zapier account and create a new automation (aka "Zap").

check Select Killswitch as the Trigger

Search for the Killswitch integration and use it as the "Trigger" (starting point) for your workflow.

Select the "New Order" as your trigger event (starting point).

check Enable Zapier to conect to Killswitch

Connect Zapier to your Killswitch account by entering the Killswitch API Key generated in Step 1.

check Configure the Killswitch Order selection option

Select what type of Killswitch Orders you want to use in your automation. You can choose from: "Get Orders Paid", "Get Orders With Payment Error", "Get Orders Without Payment"

check Select and configure the target application (Action)

Search for the application that will use the information from the Killswitch order to perform a new action.

Configure your target action by mapping the data from the Killswitch order to fields in the target application. I.e.the Killswitch field "customer_fiscal_id" might be mapped to your ERP field "vatNumber"

The target action and fields in your automation will be dependent on the data made available by Killswitch (order data) as well as the fields available to be used in the target application

The data fields made available by Killswitch for every order are the following:

Technical name Data type Description
id String Order Id - unique within the Killswitch application. 18 char length.
order_number String Order number - unique within the Killswitch application. Contains leading zeroes.
created_date Date/time Date / time when order was created
last_modified_date Date/time Date / time when order was last modified
currency_code String 3 char currency ISO code
status String Order overall status. Available statuses are: "Paid", "Payment error", "Created", "Pay-per-use (in progress)", "Pay-per-use (finished)".
payment_status String Order payment status. Available statuses are: "Paid", "Pending", "Canceled", "N/A".
order_pin String Order PIN. Used by customer to access an ongoing order / charging session. Also used in the credit card / mobile payment description to identify a specific Order. The Order PIN is not unique.
usage_unit String Usage unit / Order unit. Possible values are: "Minute", "Hour", "Day", "15 Min", "30 Min", "kWh".
language String Customer language. 2 chars language code. The language is set by the browser used by the user to access the Killswitch checkout. Possible values are: "en" (default), "fr", "es", "pt", "de".
origin String Order origin. Possible values are: "Checkout (online)", "RFID Tag", "Created manually (Dashboard)"
discount_code String Discount code used by customer at the checkout. Max 6 chars.
customer_name String Info collected from customer:
Name.
customer_company_name String Info collected from customer:
Company name.
customer_address String Info collected from customer:
Address (street)
customer_city String Info collected from customer:
City
customer_postal_code String Info collected from customer:
Postal code
customer_country_code String Info collected from customer:
Country code (2 chars)
customer_fiscal_id String Info collected from customer:
Fiscal ID / VAT Number
customer_license_plate String Info collected from customer:
License plate
customer_email String Info collected from customer:
Email
customer_phone String Info collected from customer:
Phone number
customer_apartment_no String Info collected from customer:
Apartment / house number
customer_room_no String Info collected from customer:
Room number (hotel)
customer_custom_info_descr String Custom info to be collected from customer:
Custom info description
customer_custom_info String Info collected from customer:
Custom info
stop_reason String Charging session stop reason. Received from the OCPP "StopSession" information.
refund_reason String Refund reason (description).
device_id String Device (charger) information:
Device Id. Unique within the Killswitch application.
device_name String Device (charger) information:
Device name.
device_type String Device (charger) information:
Device type. Possible values are: "OCPP", "relay" (Shelly® device)
device_ocpp_identity String Device (charger) information:
OCPP identity.
device_tech_id String Device (charger) information:
Device technical Id.
tag_id String RFID Tag information:
Internal Killswitch Tag Name.
tag_rfid String RFID Tag information:
RFID Tag Id.
tag_company_name String RFID Tag information:
Company name.
tag_user_name String RFID Tag information:
User / customer name.
tag_user_email String RFID Tag information:
User / customer email.
tag_license_plate String RFID Tag information:
User / customer license plate.
quantity Number Order quantity.
unit_price Number Order unit price.
time_zone_offset Number Time-zone offset in hours. May contain decimals.
min_usage Number Minimum order quantity.
max_usage Number Maximum order quantity. Does not apply for pay-per-use orders.
usage_duration_secs Number Expected order duration in seconds. Integer (no decimals).
effective_usage_duration_secs Number Effective order duration in seconds. Integer (no decimals).
total_amount Number Total order amount.
sub_total Number Order sub-total amount.
platform_fee Number Killswitch transaction fee.
discount_pct Number Discount percentage used to calculate the discount value, if/when Customer uses a discount code during the order checkout.
discount_value Number Discount value calculated if/when Customer uses a discount code during the order checkout.
save_our_planet_value Number "Save our Planet" initiative amount collected in this order.
meter_start Number Meter start (kWh) provided by the OCPP charger on "StartTransaction".
meter_end Number Meter end (kWh) provided by the OCPP charger on "StopTransaction".
metered_usage Number Metered usage in kWh - calculated from the "Meter end" minus "Meter start".
refund_amount Number Amount refunded.
connector_id Number OCPP Connector Id.
usage_start Date/time Order start date / time.
usage_end Date/time Order end date / time.
manually_disconnected_on Date/time Date / time when charging session was manually ended by Customer on the Killswitch checkout.
confirmed_start Date/time Confirmed order start date / time as provided by the OCPP Charger on "StartTransaction".
confirmed_end Date/time Confirmed order end date / time as provided by the OCPP Charger on "StopTransaction".
pay_per_use Boolean Order is pay-per-use.
payment_active Boolean Order is subject to payment.
charge_platform_fee Boolean Killswitch transaction fee is to be added to the total order amount.
invoice_requested Boolean Customer has requested an invoice for this order.
donated_save_our_planet Boolean Customer has donated an amount to the "Save our Planet" initiative for this order.
refunded Boolean Order has been refunded.
usage_active Boolean Order is in progress (not finished yet).
Integrate Killswitch with Zapier step 1
Integrate Killswitch with Zapier step 2
Integrate Killswitch with Zapier step 3
API Technical Details

To learn more about the technical details of the Killswitch API for Zapier please refer to the Killswitch API for Zapier page.

Need help or have questions about the Zapier integration?

Contact support