Actions20
Overview
This node integrates with the Housecall Pro API to manage various resources such as applications, customers, jobs, and more. Specifically, for the Application resource and the Create Address operation (which is actually under the Customer resource in this implementation), it allows creating a new address associated with a specific customer by sending the relevant address details to the API.
Common scenarios where this node is beneficial include:
- Automating customer data management workflows by programmatically adding addresses to customer profiles.
- Integrating Housecall Pro customer address management into broader business automation processes.
- Keeping customer contact information up-to-date without manual entry.
For example, you might use this node to add a new service location address for a customer when they request work at a different site.
Properties
| Name | Meaning |
|---|---|
| Resource | The type of entity to interact with; here, "Application" or "Customer" (address creation is under Customer). |
| Operation | The action to perform; for address creation, it's post-customer-customer_id-addresses which means creating an address for a customer. |
| Customer ID | The unique identifier of the customer to whom the new address will be added. |
| Address Details | A collection of fields describing the address to create: |
| - Street | Primary street address line. |
| - Street Line 2 | Secondary street address line (optional). |
| - City | City name. |
| - State | State or region. |
| - Zip | Postal code. |
| - Country | Country name (default is "USA"). |
The provided input properties JSON only includes a hidden property related to application operation routing, but the bundled source code reveals the full set of properties relevant to creating a customer address.
Output
The node outputs the response from the Housecall Pro API after creating the address. This output is available in the json field of the node's output data and typically contains the newly created address object with its assigned ID and all submitted address details.
If the API supports binary data for any resource (not indicated here), the node would also handle that accordingly, but for address creation, the output is purely JSON.
Dependencies
- Requires an active connection to the Housecall Pro API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for API requests is
https://api.housecallpro.com. - No additional external dependencies are required beyond the API access.
Troubleshooting
- Missing or invalid Customer ID: The operation requires a valid customer ID. Ensure the ID exists and is correctly passed.
- Incomplete address details: Some address fields may be mandatory on the API side. Verify that required fields like street, city, state, zip, and country are provided.
- Authentication errors: If the API key or token is missing or invalid, the node will fail to authenticate. Check credentials configuration.
- API rate limits or downtime: The Housecall Pro API may throttle requests or be temporarily unavailable. Retry later or check API status.
- Unexpected API responses: If the API changes or returns errors, inspect the raw response for clues and update the node or workflow accordingly.