Actions20
Overview
The "Disable Application" operation under the "Customer" resource is designed to disable the application for a company via the Housecall Pro API. This node action sends a request to the API endpoint responsible for disabling the application, effectively turning off or suspending the application's functionality for that company.
This operation is useful in scenarios where a company needs to temporarily or permanently deactivate their access or usage of the Housecall Pro application, such as during maintenance, account suspension, or when discontinuing service.
Practical example:
- A business wants to suspend its Housecall Pro application access due to non-payment or policy violations.
- An administrator automates disabling the application for multiple companies based on certain triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| Resource | The main entity type to interact with; here it should be set to "Application". |
| Operation | The specific action to perform; here it is "Disable Application". |
| Additional Fields | Optional additional parameters for the disable request (currently no specific fields). |
Note: For this operation, the input properties are minimal since disabling the application typically requires only authentication and possibly some optional parameters.
Output
The output JSON will contain the response from the Housecall Pro API after attempting to disable the application. This usually includes status information about the success or failure of the disable request.
The node does not explicitly handle binary data for this operation.
Dependencies
- Requires an active connection to the Housecall Pro API.
- Requires an API key credential configured in n8n for authenticating requests to Housecall Pro.
- The base URL used for API requests is
https://api.housecallpro.com. - Proper permissions must be granted to the API key to allow disabling the application.
Troubleshooting
Common issues:
- Invalid or missing API credentials can cause authentication failures.
- Insufficient permissions for the API key may result in authorization errors.
- Network connectivity problems can prevent reaching the Housecall Pro API.
- Attempting to disable an already disabled application might return an error or no-op response.
Common error messages:
- 401 Unauthorized: Check that the API key credential is correctly configured and valid.
- 403 Forbidden: Ensure the API key has permission to disable applications.
- 404 Not Found: Verify the correct endpoint and that the application exists.
- 500 Internal Server Error: Retry later or contact Housecall Pro support if persistent.
Links and References
- Housecall Pro API Documentation
- n8n Documentation on HTTP Request Node (for understanding API calls)