Pitstop is a fleet management platform that helps you monitor asset health, schedule preventive maintenance, and catch issues — like fault codes and Driver Vehicle Inspection Report (DVIR)-reported defects — before they cause breakdowns.
This means your team can plan repairs earlier instead of reacting to emergencies. For example, if a unit shows signs of a failing component, Pitstop can flag the issue and create a Service Request in Fullbay so your shop can fix it before the unit is down on the road.
Continue reading below to learn how the Pitstop integration works, what to expect during setup, and how to confirm it is active.
Permissions
Permissions
Before continuing, users may require the following permission(s) to complete the task(s) mentioned in this article.
Permission | Description |
Manage Fullbay Connect | When enabled, users can view and edit the Fullbay Connect page. |
View & Edit Customers (Including Customer Payments) and Units | With this permission, users will be able to view and edit:
⚠️ You do not need this permission to add a customer when creating a Service Order or Quick Service Order. |
*Full User Only permission.
Before You Get Started
Before using the Pitstop integration, there are a few important things to know about how it works in Fullbay.
The Pitstop integration is set up during onboarding by the Fullbay team
Your shop must have Pitstop included in your Fullbay plan or subscription
Once enabled, the integration connects Pitstop and Fullbay using API keys
Important | Pitstop is not a self-service integration. If you do not see it in your account, contact your Fullbay representative for help.
Benefits
Here are the main ways Pitstop helps your shop:
Catch Issues Early | Pitstop identifies problems before they cause breakdowns, giving your team time to plan repairs instead of reacting to emergencies.
Reduce Unplanned Downtime | By creating Service Requests automatically, your shop can address issues sooner and keep units on the road.
Improve Shop Efficiency | Your team does not need to enter issues manually. Pitstop sends the data into Fullbay, so your team can focus on diagnosing and fixing the problem.
Example | A fault code is detected on a truck in Pitstop. Instead of waiting for a breakdown, a Service Request is created in Fullbay. Your shop schedules the repair ahead of time and avoids a roadside failure.
How the Pitstop Integration Works
Once Pitstop is connected to Fullbay:
Pitstop detects an issue, such as a defect or fault code
The issue is sent to Fullbay
A Service Request is created for your shop
Your team reviews and converts the Service Request into a Service Order
As work progresses, updates are sent back to Pitstop
This creates a clear workflow from issue detection to repair completion, helping your shop stay organized and proactive.
Confirm Pitstop is Available
You can check if Pitstop is available for your shop by following these steps:
Click on your name or image at the top right-hand corner of the screen and select Integrations.
Scroll to the Marketing & Communication section and locate the Pitstop card.
Note | The Pitstop integration card only appears if Pitstop is included in your plan or subscription.
Connect Pitstop to a Customer
After the integration is enabled, you must connect Pitstop to each customer.
Navigate to the Service page and select the Customers tab.
Select a customer and navigate to the Details tab.
Scroll to the Pitstop section and click Connect.
Enter the Pitstop API Key provided by your customer.
Click Save.
After saving:
A Fullbay API Key is generated automatically
The connection between Pitstop and Fullbay is established
Important | Both API keys are required to allow data to move between Pitstop and Fullbay.
What Happens After Setup
Once Pitstop is connected:
Service Requests are created automatically when issues are detected.
These requests appear in the Service page like any other Service Request.
Your team can review, assign, and convert them into Service Orders.
Pitstop Service Requests in Fullbay
When Pitstop detects an issue, it creates a Service Request in Fullbay automatically. No manual entry is needed. Here is what to expect when one arrives.
Each Service Request from Pitstop includes the following pre-filled information:
The unit’s Year, Make, Model, and VIN
The complaint or problem description, pulled directly from the Pitstop defect or fault code
The shop the request is assigned to
Because Pitstop creates these requests automatically, the Created By field will be blank. This is the easiest way to identify a Service Request that came from Pitstop.
Multiple Defects, One Service Request
If Pitstop sends multiple defects from the same inspection at the same time, they all arrive as Action Items on a single Service Request — not as separate requests. This keeps related issues grouped together so your team can review and address them efficiently.
How Fullbay Updates Pitstop
Fullbay automatically sends status updates back to Pitstop at two points in the workflow:
When the Service Request is converted to a Service Order
When the Service Order is invoiced
This keeps both systems in sync without any manual updates from your team.
Learn More | To review, edit, or convert a Pitstop Service Request, follow the same steps as any other Service Request. See Service Requests in Help & Training for details.
Helpful Tips
What happens if Pitstop is removed from my plan? | The integration will no longer be available, and new Service Requests will not be created from Pitstop.
For More Information
Continue exploring the Pitstop collection to learn more about using Pitstop with Fullbay.