Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

MotionTools

Digitize processes, boost efficiency and excite users with MotionTools, the operating system for fleet-based service providers.

CategoryOther
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect MotionTools with Flows360

Digitize processes, boost efficiency and excite users with MotionTools, the operating system for fleet-based service providers.

Use the MotionTools connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 2 actions and 5 triggers.

Available actions

  • Create 1-stop Booking
  • Create 2-stop Booking

Available triggers

  • Booking Created
  • Booking Status Update
  • Booking Stop Status Update
  • Package Created
  • Package Status Update

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: MotionTools
  • Package: @activepieces/piece-motiontools@0.1.7
  • Exact artifact digest: sha256:41dac96205fb259241a1dd351d4bbdc1ed30bbcb7f5cd7f369fcbd59497cc99e
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create 1-stop Booking (create1stopBooking), Create a hailing booking (1-stop). Classification: read.
  • Create 2-stop Booking (create2stopBooking), Create a hailing booking with two stops (pickup + dropoff). Classification: read.

Trigger contracts

  • Booking Created, webhook.
  • Booking Status Update, webhook.
  • Booking Stop Status Update, webhook.
  • Package Created, webhook.
  • Package Status Update, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actions2
Triggers5

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Motiontools API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create 1-stop Booking Yes No Create a hailing booking (1-stop).
Create 2-stop Booking Yes No Create a hailing booking with two stops (pickup + dropoff).
Booking Created Yes No webhook trigger declared by the pinned package.
Booking Status Update Yes No webhook trigger declared by the pinned package.
Booking Stop Status Update Yes No webhook trigger declared by the pinned package.
Package Created Yes No webhook trigger declared by the pinned package.
Package Status Update Yes No webhook trigger declared by the pinned package.

Supported actions

Create 1-stop Booking · Read

Create a hailing booking (1-stop).

create1stop_booking · Risk: low · Retry: safe

Inputs

  • scheduled_at · string · Optional, Scheduled datetime (ISO 8601) for the booking (optional)
  • payment_method · string · Required, Payment method (e.g. cash, card)
  • stop_type · string · Optional, Type of stop (e.g. pickup, dropoff)
  • stop_lat · number · Optional, Latitude for the stop (optional)
  • stop_lng · number · Optional, Longitude for the stop (optional)
  • stop_street · string · Optional, Street name for the stop (optional)
  • stop_number · string · Optional, Street number for the stop (optional)
  • stop_city · string · Optional, City for the stop (optional)
  • stop_country · string · Optional, Country for the stop (optional)
  • stop_zip_code · string · Optional, Postal code for the stop (optional)
  • stop_additional_line · string · Optional, Additional address line for the stop (optional)
  • stop_location_name · string · Optional, Location name for the stop (optional)
  • stop_first_name · string · Optional, Contact's first name at the stop (optional)
  • stop_last_name · string · Optional, Contact's last name at the stop (optional)
  • stop_phone_number · string · Optional, Contact's phone number (optional)
  • stop_email · string · Optional, Contact's email (optional)
Create 2-stop Booking · Read

Create a hailing booking with two stops (pickup + dropoff).

create2stop_booking · Risk: low · Retry: safe

Inputs

  • scheduled_at · string · Optional, Scheduled datetime (ISO 8601) for the booking (optional)
  • payment_method · string · Required, Payment method (e.g. cash, card)
  • additional_information · string · Optional, Any extra notes for the booking (optional)
  • metadata · object · Optional, Additional metadata for the booking (optional)
  • stop1_type · string · Optional
  • stop1_metadata · object · Optional
  • stop1_lat · number · Optional
  • stop1_lng · number · Optional
  • stop1_street · string · Optional
  • stop1_number · string · Optional
  • stop1_city · string · Optional
  • stop1_country · string · Optional
  • stop1_zip_code · string · Optional
  • stop1_additional_line · string · Optional
  • stop1_location_name · string · Optional
  • stop1_first_name · string · Optional
  • stop1_last_name · string · Optional
  • stop1_phone_number · string · Optional
  • stop1_email · string · Optional
  • stop2_type · string · Optional
  • stop2_metadata · object · Optional
  • stop2_lat · number · Optional
  • stop2_lng · number · Optional
  • stop2_street · string · Optional
  • stop2_number · string · Optional
  • stop2_city · string · Optional
  • stop2_country · string · Optional
  • stop2_zip_code · string · Optional
  • stop2_additional_line · string · Optional
  • stop2_location_name · string · Optional
  • stop2_first_name · string · Optional
  • stop2_last_name · string · Optional
  • stop2_phone_number · string · Optional
  • stop2_email · string · Optional

Triggers

Booking Created · Webhook

Triggers when a new booking is created. Only available if you have a MotionToolsadmin account

Inputs

  • instructions · string
Booking Status Update · Webhook

Triggers when a booking status is updated. Only available if you have a MotionToolsadmin account

Inputs

  • instructions · string
Booking Stop Status Update · Webhook

Inputs

  • instructions · string
Package Created · Webhook

Triggers when a package is created

Inputs

  • instructions · string
Package Status Update · Webhook

Inputs

  • instructions · string

Setup

Setup

  1. Add the MotionTools connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-motiontools@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required MotionTools connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-motiontools@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com