DIMO is an open protocol using blockchain to establish universal digital vehicle identity, permissions, data transmission, vehicle control, and payments. Developers use DIMO to build apps based on connected vehicles around the world while the vehicle owners benefit from monetizing their vehicle data.
DIMO currently provides 9 triggers that can start a workflow and 38 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Battery is Charging Trigger
Triggers when vehicle battery charging status changes (True/False).
Battery Current Power Trigger
Triggers when vehicle battery current power meets the specified condition.
Charge Level Trigger
Triggers when vehicle battery charge level meets the specified condition.
Fuel System Absolute Level Trigger
Triggers when vehicle fuel system absolute level meets the specified condition.
Fuel System Relative Level Trigger
Triggers when vehicle fuel system relative level meets the specified condition.
Ignition Status Trigger
Triggers when vehicle ignition status changes (ON/OFF).
Odometer Trigger
Triggers when vehicle odometer meets the specified condition.
Speed Trigger
Triggers when vehicle speed meets specified conditions.
Tire Pressure Trigger
Triggers when vehicle tire pressure meets the specified condition.
Attestation : Create VIN VC
Generates the VIN VC for a given vehicle.
Device Definitions : Decode VIN
Submits a decoding request for vehicle identification number, returns the device definition ID corresponding to the VIN.
Device Definitions : Lookup
Search for device definitions by query and filters.
Token Exchange : Get Vehicle JWT
Creates a token exchange to obtain a Vehicle JWT.
Identity : Custom Query
Custom Identity Query.
Identity : Total Vehicle Count
Get total vehicle count.
Identity : Get Developer License Info
Get developer license info by tokenId.
Identity : Get Vehicle By Dev License
Get vehicles by developer license 0x address.
Identity : Get Total Vehicle Count For Owner.
Get total vehicle count for an owner.
Identity : Get Vehicle MMY By Owner
Get vehicle MMY by owner address.
Identity : Get Vehicle MMY By TokenId
Get vehicle MMY by tokenId.
Identity : Get SACD For Vehicle
Get SACD for a vehicle by tokenId.
Identity : Get Rewards By Owner
Get rewards by owner address.
Identity : Get Reward History By Owner
Get reward history by owner address.
Identity : Get Device Definition
Get device definition by vehicle tokenId.
Identity : Get Device Definition By DefinitionId
Get device definition by definitionId.
Identity : Get Owner Vehicles
Get vehicles owned by an address.
Identity : Get Developer Shared Vehicles From Owner
Get vehicles shared with a developer license from an owner.
Identity : Get DCNs By Owner
Get DCNs by owner address.
Telemetry : Custom Query
Query DIMO Telemetry API using a custom GraphQL query.
Telemetry : Available Signals
Get a list of available signals for a specific vehicle.
Telemetry : Signals
Get a selection of available signals for a specific vehicle.
Telemetry : Daily Avg Speed
Get the average speed of a vehicle over a specific time period.
Telemetry: Events
Get the vehicle events over a specific time period.
Telemetry : Max Speed
Get the maximum speed of a vehicle over a specific time period.
Telemetry : VIN VC Latest
Get the latest VIN and Vehicle Configuration for a specific vehicle.
Vehicle Events: List Webhooks
List all webhooks.
Vehicle Events: Create/Update Webhook (Numeric)
Create a new webhook or update existing one for numeric vehicle signals. If Webhook ID is provided, it will update; otherwise, it will create a new webhook.
Vehicle Events: Create/Update Webhook (Boolean)
Create a new webhook or update existing one for boolean vehicle signals. If Webhook ID is provided, it will update; otherwise, it will create a new webhook.
Vehicle Events: Create/Update Webhook (Events)
Create a new webhook or update existing one for vehicle events like harsh braking, acceleration, etc. If Webhook ID is provided, it will update; otherwise, it will create a new webhook.
Vehicle Events: Delete Webhook
Delete a webhook.
Vehicle Events: List Signals
List all signals.
Vehicle Events: List Subscribed Vehicles
List vehicles subscribed to a webhook.
Vehicle Events: List Vehicle Subscriptions
List all subscriptions for a vehicle.
Vehicle Events: Subscribe Vehicle
Subscribe a vehicle to a webhook.
Vehicle Events: Subscribe All Vehicles
Subscribe all vehicles to a webhook.
Vehicle Events: Unsubscribe Vehicle
Unsubscribe a vehicle from a webhook.
Vehicle Events: Unsubscribe All Vehicles
Unsubscribe all vehicles from a webhook.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported DIMO event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Battery is Charging Trigger
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported DIMO action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Attestation : Create VIN VC
Combine DIMO with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
Battery is Charging Trigger
Finishes with
Attestation : Create VIN VC, then preserve the outcome in Coherence
The exact authentication fields depend on DIMO. The workflow structure stays straightforward:
Authorize the DIMO account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with DIMO or provide a complementary trigger or action.
DIMO currently provides 9 triggers that can start a workflow and 38 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
DIMO currently lists 9 triggers and 38 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported DIMO triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
