Actions20
Overview
This node integrates with the Housecall Pro API to manage various resources related to service businesses, such as applications, customers, jobs, invoices, and more. Specifically, for the Application resource with the Update operation (which corresponds to enabling or disabling the application), it allows users to enable or disable the Housecall Pro application for a company via API calls.
Common scenarios where this node is beneficial include automating the activation or deactivation of the Housecall Pro application within workflows, such as onboarding new companies by enabling the app or suspending services by disabling it.
Practical example:
- Automatically enable the Housecall Pro application for a newly onboarded company.
- Disable the application when a company’s subscription expires or is paused.
Properties
| Name | Meaning |
|---|---|
| Application Operation Routing | Internal routing configuration mapping operations to HTTP methods and API endpoints: - get-applications: GET /application - post-application-enable: POST /application/enable - post-application-disable: POST /application/disable |
Note: The provided properties JSON only includes hidden routing information for the Application resource operations. The actual user-facing input fields for enabling or disabling the application are not explicitly defined here, implying that no additional parameters are required beyond selecting the operation.
Output
The node outputs JSON data representing the response from the Housecall Pro API after performing the requested operation on the Application resource. This typically includes confirmation of the action taken (e.g., success status of enabling or disabling the application) and any relevant metadata returned by the API.
No binary data output is indicated in the source code.
Dependencies
- Requires an active connection to the Housecall Pro API.
- Needs an API authentication token or key configured in n8n credentials (referred generically as "an API key credential").
- The base URL for API requests is
https://api.housecallpro.com. - The node sends and expects JSON-formatted data.
Troubleshooting
Common issues:
- Authentication failures due to missing or invalid API credentials.
- Network connectivity problems preventing access to the Housecall Pro API.
- Attempting to enable or disable the application without proper permissions.
Common error messages:
- Unauthorized or 401 errors: Check that the API key credential is correctly set up and has necessary permissions.
- 404 Not Found: Verify that the API endpoint URLs have not changed or that the resource exists.
- 400 Bad Request: Ensure that all required parameters (if any) are correctly provided.
Resolving these usually involves verifying API credentials, checking network connectivity, and confirming that the selected operation matches the intended API endpoint.
Links and References
- Housecall Pro API Documentation (for detailed API endpoints and request/response formats)
- n8n documentation on creating custom nodes