Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Accounts → Invite User To Account
AI-generatedOverview
This node operation allows you to invite a user to an existing account by sending an invitation email with a specified role and optional personal details. It is useful in scenarios where you need to programmatically add users to an account within a system, such as onboarding new team members or collaborators with defined access levels.
Practical examples include:
- Automatically inviting new employees to a company account with the "Employee" role.
- Adding accounting personnel to an account with restricted permissions.
- Granting admin access to a partner or manager by sending them an invitation.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the user will be invited. |
| Email address of the user to invite. | |
| Role | Role assigned to the invited user. Options: Admin, Accounting, Employee. |
| First Name | (Optional) First name of the invited user. |
| Last Name | (Optional) Last name of the invited user. |
Output
The node outputs JSON data representing the result of the invitation request. This typically includes confirmation details about the invited user or the status of the invitation process. The exact structure depends on the API response but generally contains fields like user ID, email, role, and invitation status.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authentication with the external service managing accounts and users.
- The node uses HTTP requests with JSON payloads to interact with the external API.
- Proper configuration of the base URL and authentication credentials in n8n is necessary.
Troubleshooting
- Common issues:
- Invalid or missing Account Id can cause the invitation to fail.
- Incorrect or malformed email addresses may lead to errors or undelivered invitations.
- Insufficient permissions associated with the API key might prevent user invitations.
- Error messages:
- "Account not found" indicates the provided Account Id does not exist or is inaccessible.
- "Invalid email format" suggests the email property is not correctly formatted.
- "Unauthorized" or "Forbidden" errors imply authentication or permission problems; verify API credentials and roles.
- To resolve these, ensure all required properties are correctly set, validate email formats, and confirm that the API key has adequate permissions.
Links and References
- Refer to the external API documentation for detailed information on user invitation endpoints and role definitions.
- Consult n8n documentation on setting up API credentials and HTTP request nodes for further customization.