mfr Trigger
AI-generatedOverview
This node acts as a trigger for workflows based on events from the MFR system. It listens for specific webhook events such as new appointments, new companies, new service objects, new service requests, or changes in service request states. When such an event occurs, the node activates the workflow, passing the event data along. This is useful for automating processes that depend on real-time updates from the MFR platform, such as scheduling, notifications, or data synchronization.
Use Case Examples
- Trigger a workflow when a new appointment is created in the MFR system to send a confirmation email.
- Start a workflow when a new company is added to update a CRM system.
- Activate a workflow when a service request state changes to notify the relevant team.
Properties
| Name | Meaning |
|---|---|
| WebHookType | Specifies the type of MFR event to listen for, such as New Appointment or New Company. |
| ExternalId | An optional external identifier to filter webhook events by a specific external ID. |
Output
JSON
body- The JSON payload received from the MFR webhook event, containing event-specific data.
Dependencies
- Requires an API key credential for the MFR API to manage webhook registration and authentication.
Troubleshooting
- If the webhook does not trigger, verify that the webhook URL is correctly registered in the MFR system and that the WebHookType and ExternalId parameters match the expected event.
- Common errors include failure to create or delete webhooks due to API permission issues or incorrect API credentials. Ensure the API key is valid and has the necessary permissions.
- If no events are received, check network connectivity and that the MFR system is sending events to the correct callback URL.
