Motive
Manage Motive fleet vehicles, vehicle locations, drivers, users, and company webhook events.
Tools
| Name | Description |
|---|---|
list_vehicle_locationsList Motive vehicle locations through the v3 Vehicle Gateway endpoint. Use filters for least-privilege location reads. | List Motive vehicle locations through the v3 Vehicle Gateway endpoint. Use filters for least-privilege location reads. |
list_vehiclesList Motive company vehicles, optionally restricted to vehicles updated after a UTC timestamp. | List Motive company vehicles, optionally restricted to vehicles updated after a UTC timestamp. |
get_vehicleFetch one Motive vehicle by exact vehicle ID. | Fetch one Motive vehicle by exact vehicle ID. |
create_vehicleCreate a Motive vehicle using the documented vehicle body. Include gateway and external ID details when required by your account. | Create a Motive vehicle using the documented vehicle body. Include gateway and external ID details when required by your account. |
update_vehicleUpdate a Motive vehicle by exact vehicle ID using documented vehicle fields. | Update a Motive vehicle by exact vehicle ID using documented vehicle fields. |
list_driver_locationsList Motive drivers with current location and vehicle information. Use bounded pages for PII-heavy operations. | List Motive drivers with current location and vehicle information. Use bounded pages for PII-heavy operations. |
create_userCreate a Motive user such as a driver, fleet user, or admin using the documented user body. | Create a Motive user such as a driver, fleet user, or admin using the documented user body. |
update_userUpdate a Motive user by exact user ID. | Update a Motive user by exact user ID. |
Triggers
| Name | Description |
|---|---|
vehicle_location_updatedPoll Motive vehicle locations after an initial baseline. | Poll Motive vehicle locations after an initial baseline. |
webhook_event_receivedReceive Motive company webhook events. Signature verification is not performed by this trigger. | Receive Motive company webhook events. Signature verification is not performed by this trigger. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('motive', 'list_vehicle_locations', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'motive',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
How do I connect Motive to my app?
Use Weavz Hosted Connect for API Key authentication. Install the SDK, create a connection through the connect portal or API, then execute tools programmatically.
What tools does Motive support?
Motive supports 8 tools including List Vehicle Locations, List Vehicles, Get Vehicle, Create Vehicle, Update Vehicle, and more.
Can I use Motive with AI agents?
Yes. Add Motive to an MCP server in Tool Mode or Code Mode. Code Mode provides 3 meta-tools with on-demand API discovery so agents can compose stateful workflows without loading every action schema up front.
Can Motive be used in stateful agent workflows?
Yes. Agents can combine Motive tools with Filesystem, State KV, Human Gates, input partials, and other workspace integrations while keeping execution scoped to the selected workspace or end user.
What authentication does Motive use?
Motive uses API Key. Weavz stores credentials securely and uses them for authorized action execution.
How much does the Motive integration cost?
The Motive integration is included on all Weavz plans including the free tier with 20,000 actions per month. No credit card required.
What triggers does Motive support?
Motive supports 2 triggers including Vehicle Location Updated, Webhook Event Received.
Connect Motive in minutes
Get 20,000 free action executions every month. No credit card required.