Use case: Integrating Simply CRM with Mobilplan.nu
Integrating Simply CRM with Mobilplan.nu allows you to streamline your business processes by synchronizing data between
the two platforms. By utilizing webhooks from Simply CRM, you can easily connect the two systems and automate various
operations, such as updating customers, managing projects, tracking time registrations, and much more.
In this Use Case we will integrate Simply CRM and Mobilplan.nu using Webhooks - if you do not already know how to use
Webhooks in Simply CRM, we suggest you just read our introduction to Webhooks first.
Setting Up the Integration
To integrate Simply CRM with Mobilplan.nu, you will need to configure webhooks in Simply CRM to trigger API calls to
Mobilplan. These API calls will include data from Simply CRM that can then be used in Mobilplan to keep your records up
to date.
When making API calls to Mobilplan, make sure to include the Username, Password, and API Key in the header of each
request. These credentials are essential for authenticating your requests and ensuring secure communication between the
two platforms.
Mobilplan.nu has provided a basic API documentation at:
https://mobilplan.nu/api/
Relevant Endpoints
Here are some of the key Mobilplan API endpoints that are most useful for integrating with Simply CRM. These endpoints
will allow you to manage customer data, projects, time registrations, and more.
Below is a list of key Mobilplan.nu API endpoints that are pertinent for integration with Simply CRM:
1. Customers
- Purpose: Manage customer records.
- Endpoint: /customer
- Methods:
- GET /customer: Retrieve a list of customers.
- POST /customer: Create a new customer.
- PATCH /customer/{id}: Update an existing customer's information.
- DELETE /customer/{id}: Delete a customer record.
2. Files
- Purpose: Handle file uploads and management.
- Endpoint: /file
- Methods:
- GET /file: Retrieve a list of files.
- POST /file: Upload a new file.
- DELETE /file/{id}: Delete a file.
3. Quality Assurance Forms
- Purpose: Manage quality assurance forms.
- Endpoint: /qualityassuranceform
- Methods:
- GET /qualityassuranceform: Retrieve a list of QA forms.
- POST /qualityassuranceform: Create a new QA form.
- PATCH /qualityassuranceform/{id}: Update an existing QA form.
- DELETE /qualityassuranceform/{id}: Delete a QA form.
4. Hour Types
- Purpose: Manage different types of work hours.
- Endpoint: /hourtype
- Methods:
- GET /hourtype: Retrieve a list of hour types.
- POST /hourtype: Create a new hour type.
- PATCH /hourtype/{id}: Update an existing hour type.
- DELETE /hourtype/{id}: Delete an hour type.
5. Installations
- Purpose: Manage installation records.
- Endpoint: /installation
- Methods:
- GET /installation: Retrieve a list of installations.
- POST /installation: Create a new installation record.
- PATCH /installation/{id}: Update an existing installation.
- DELETE /installation/{id}: Delete an installation record.
6. Materials
- Purpose: Manage material records.
- Endpoint: /material
- Methods:
- GET /material: Retrieve a list of materials.
- POST /material: Add a new material.
- PATCH /material/{id}: Update an existing material's details.
- DELETE /material/{id}: Delete a material record.
7. Registrations
- Purpose: Manage various types of registrations.
- Endpoint: /registration
- Methods:
- GET /registration: Retrieve a list of registrations.
- POST /registration: Create a new registration.
- PATCH /registration/{id}: Update an existing registration.
- DELETE /registration/{id}: Delete a registration.
8. Messages
- Purpose: Manage communication messages.
- Endpoint: /message
- Methods:
- GET /message: Retrieve a list of messages.
- POST /message: Send a new message.
- PATCH /message/{id}: Update an existing message.
- DELETE /message/{id}: Delete a message.
9. Offers
- Purpose: Manage offer records.
- Endpoint: /offer
- Methods:
- GET /offer: Retrieve a list of offers.
- POST /offer: Create a new offer.
- PATCH /offer/{id}: Update an existing offer.
- DELETE /offer/{id}: Delete an offer.
10. Projects
- Purpose: Manage project records.
- Endpoint: /project
- Methods:
- GET /project: Retrieve a list of projects.
- POST /project: Create a new project.
- PATCH /project/{id}: Update an existing project's details.
- DELETE /project/{id}: Delete a project.
11. Project Status Log
- Purpose: Track changes in project statuses.
- Endpoint: /projectstatuslog
- Methods:
- GET /projectstatuslog: Retrieve a list of project status logs.
- POST /projectstatuslog: Create a new project status log entry.
12. Rentals
- Purpose: Manage rental records.
- Endpoint: /rental
- Methods:
- GET /rental: Retrieve a list of rentals.
- POST /rental: Create a new rental record.
- PATCH /rental/{id}: Update an existing rental.
- DELETE /rental/{id}: Delete a rental record.
13. Schematics
- Purpose: Retrieve schema definitions for data structures.
- Endpoint: /schematics
- Methods:
- GET /schematics: Retrieve schema definitions.
14. Units
- Purpose: Manage unit records.
- Endpoint: /unit
- Methods:
- GET /unit: Retrieve a list of units.
- POST /unit: Create a new unit.
- PATCH /unit/{id}: Update an existing unit.
- DELETE /unit/{id}: Delete a unit.
Searching for Records
If you need to search for specific records such as offers, Mobilplan provides a JSON-based format for making these
searches. For example, you can search for offers that were updated on a specific date with a request like this:
https://api-1.mps1.mobilplan.nu/offers/{"updated_on": "2024-11-04"}/1
If you want to add a condition like searching for records updated after a certain date, you can include a greater-than
(>) operator in the search query:
ttps://api-1.mps1.mobilplan.nu/offers/{"updated_on":{"operator":">","value":"2024-11-04"}}
Conclusion
By using the above endpoints and search formats, you can fully integrate Simply CRM with Mobilplan.nu. This integration
will allow for seamless data flow between your customer management platform and your project management tool, automating
workflows and improving overall efficiency. For further details on the API, visit Mobilplan’s API Documentation.
