Actions33
- Template Actions
- Document Actions
- Signer Actions
- Background Check Actions
- Partnership Actions
- Timestamp Actions
- Webhook Actions
Overview
The node's Create Partner Account operation under the Partnership resource allows users to create a new partner company account in the ZapSign system. This operation is useful for automating the onboarding of partner companies by programmatically registering their details such as email, phone number, country, language, and company name.
Typical use cases include:
- Automatically adding new partner companies from CRM or ERP systems.
- Integrating partner account creation into onboarding workflows.
- Managing partner networks without manual data entry.
For example, a business that manages multiple partner companies can use this node to create accounts for each partner with their contact information and localization settings, streamlining partnership management.
Properties
| Name | Meaning |
|---|---|
| Email address of the new user who will be added as a member (required). | |
| Phone Number | Phone number of the new user (optional). |
| Phone Country Code | Country code for the phone number, e.g., "55" for Brazil (default: "55"). |
| Country | Country of the new account. Options: Brazil, Mexico, Colombia, Peru, Chile (required). |
| Language | Language of the new company. Options: Portuguese (Brazil), Spanish, English (required). |
| Company Name | Name of the new company (required). |
Output
The output is a JSON array where each element corresponds to the result of creating a partner account for an input item. The JSON structure typically contains the response from the ZapSign API confirming the creation of the partner company account, including any identifiers or status messages returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the ZapSign API with valid credentials (an API key or token).
- The node uses environment variables to determine the API base URL, supporting sandbox and production environments.
- No additional external services are required beyond the ZapSign API.
Troubleshooting
Common Issues
- Missing Required Fields: The operation requires
country,lang, andcompany_namefields. Omitting these will cause errors. - Invalid Email Format: If provided, the email must be valid; otherwise, the API may reject the request.
- Incorrect Country or Language Codes: Using unsupported or incorrect codes will lead to API errors.
- Phone Number Format Issues: The phone number should match the format expected for the specified country code.
Common Error Messages
- 400 Bad Request: Indicates invalid input parameters. Check that all required fields are present and correctly formatted.
- 403 Forbidden: May indicate lack of partner permissions on the account, unsupported plan features, or attempts to create accounts from another partner account. Contact ZapSign support if this occurs.
How to Resolve
- Verify all required properties are set and valid.
- Ensure the email, country, and language codes conform to expected formats.
- Confirm your ZapSign account has partner permissions enabled.
- Review API error messages for specific guidance.
Links and References
- ZapSign API Documentation (general reference for API endpoints and parameters)
- Contact ZapSign support for partner feature enablement and troubleshooting access issues.
This summary is based solely on static analysis of the provided source code and property definitions.