Zapier Actions
This page provides an overview of the Ekho Dealer actions you can use on Zapier.
Ekho Dealer Actions
Below are all the relevant Ekho Dealer actions on Zapier to help with data transfer.
What does this action do: Writes the VIN associated with a purchased vehicle to the Ekho Dealer DB.
What data does the action require:
purchasedVehicleId: Ekho Dealer’s unique identifier for the purchased vehicle associated with the VIN.vin: VIN associated with a purchased vehicle to write to Ekho Dealer
What data does this action return: the vin value.
What does this action do: Assigns the official odometer reading to the vehicle.
What data does the action require:
purchasedVehicleId: Ekho Dealer’s unique identifier for the purchased vehicle.odometerReading: Official odometer reading of the vehicle prior to sale to end consumer.
What data does this action return: the odometerReading rounded to the nearest whole number.
What does this action do: Assign the validity of the odometer reading to an object. This is used in registration and titling.
What data does the action require:
purchasedVehicleId: Ekho Dealer’s unique identifier for the purchased vehicle.odometerValidity: Indicates the odometer validity/condition. Should be one of three choices: Actual, ExceedsMechnicalLimits, NotActual. Important note: the capitalization on these three choices is important.
What data does this action return: the odometerValidity value.
What does this action do: Updates the Vehicle Fulfillment Status to one of the following: [FULFILLED, UNFULFILLED, FULFILLMENT_REQUESTED, CANCELLED].
What data does the action require:
purchasedVehicleId: Ekho Dealer’s unique identifier for the purchased vehicle.vehicleFulfillmentStatus: Indicates the fulfillment status of the vehicle. Should be one of the following choices:FULFILLED,UNFULFILLED,FULFILLMENT_REQUESTED,CANCELLED. Important note: the capitalization on these three choices is important.
What data does this action return: the vehicleFulfillmentStatus value.
What does this action do: Writes the Motorcycle Engine Number associated with a purchased vehicle to the Ekho Dealer DB.
What data does the action require:
purchasedVehicleId: Ekho Dealer’s unique identifier for the purchased vehicle.motorcycleEngineNumber: Motorcycle Engine Number associated with a purchased vehicle to write to Ekho Dealer.
What data does this action return: the motorcycleEngineNumber value.
What does this action do: Finds abandoned cart data associated with a cart id.
What data does the action require:
cartId: The cart id associated with the abandoned cart.
What data does this action return: the Abandoned Cart with the relevant data properties.
What does this action do: fetches a Placed Order from Ekho Dealer’s database.
What data does the action require:
placedOrderId: The Ekho Dealer ID of thePlaced Orderyou want to fetch.
What data does this action return: the Placed Order with the relevant data properties.
What does this action do: fetches a Purchased Vehicle from Ekho Dealer’s database
What data does the action require:
purchasedVehicleId: The Ekho Dealer ID of thePurchased Vehicleyou want to fetch.
What data does this action return: the Purchased Vehicle with the relevant data properties.
What does this action do: fetches a Purchased Accessory from Ekho Dealer’s database
What data does the action require:
purchasedAccessoryId: The Ekho Dealer ID of thePurchased Accessoryyou want to fetch.
What data does this action return: the Purchased Accessory with the relevant data properties.
What does this action do: fetches a Buyer from Ekho Dealer’s database
What data does the action require:
buyerId: The Ekho Dealer ID of theBuyeryou want to fetch.
What data does this action return: the Buyer with the relevant data properties.
What does this action do: fetches a Preorder from Ekho Dealer’s database.
What data does the action require:
preorderId: The Ekho Dealer ID of thePreorderyou want to fetch.
What data does this action return: the Preorder with the relevant data properties.