Actions19
Overview
This node integrates with the Orgo API, a multi-tenant SaaS platform for managing organizations. Specifically, the User - Create operation allows you to create a new user (member) in the Orgo system by providing their email address, first name, and last name.
Common scenarios where this node is beneficial include:
- Automating user onboarding workflows by programmatically adding new members to an organization.
- Integrating user registration from external systems or forms into Orgo.
- Bulk creating users as part of data migration or synchronization tasks.
For example, after collecting user details via a web form, you can use this node to automatically register the user in Orgo without manual intervention.
Properties
| Name | Meaning |
|---|---|
| The email address of the user (required) | |
| First Name | The first name of the user (required) |
| Last Name | The last name of the user (required) |
Output
The output JSON contains the response from the Orgo API after creating the user. This typically includes the newly created user's details such as their unique ID, email, first name, last name, status, creation timestamp, and any other metadata returned by the API.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"id": "string",
"email": "user@example.com",
"firstName": "John",
"lastName": "Doe",
"status": "active",
"createdAt": "2024-01-01T12:00:00Z"
}
Dependencies
- Requires an API key credential for authenticating with the Orgo API.
- The node expects the base URL and API token to be configured in the credentials.
- Network access to the Orgo API endpoint is necessary.
Troubleshooting
- Missing required fields: If email, first name, or last name are not provided, the API may reject the request. Ensure all required properties are set.
- Authentication errors: Invalid or missing API token will cause authentication failures. Verify that the API token credential is correctly configured.
- API endpoint unreachable: Network issues or incorrect base URL configuration can prevent successful requests.
- Error responses from API: The node returns error messages from the API in the output if
continueOnFailis enabled; otherwise, it throws exceptions. Check the error message for details.
Links and References
- Orgo API Documentation (replace with actual URL)
- n8n HTTP Request Node documentation for understanding request options: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/