Actions8
- Organizations Actions
- People Directories Actions
Overview
This node enables users to manage the status of organizations via the Pulse API. Specifically, it supports enabling or disabling an organization by updating its "enabled" status. This is useful in scenarios where organizations need to be activated or deactivated without deleting them, such as temporarily suspending access or reactivating previously disabled organizations.
Practical examples include:
- Disabling an organization that no longer participates in a service.
- Enabling a newly onboarded organization to grant access.
- Temporarily suspending an organization's activities for compliance or maintenance reasons.
Properties
| Name | Meaning |
|---|---|
| Organization ID * | The unique identifier of the organization to update. |
| Enabled | Whether the organization is enabled (true) or disabled (false). |
Output
The node outputs a JSON object representing the updated organization data after changing its status. This typically includes fields reflecting the organization's current state, including the updated "enabled" status.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Pulse API.
- The node depends on the Pulse API service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Organization ID will cause the API call to fail.
- Insufficient permissions or invalid API credentials may result in authorization errors.
- Network connectivity problems can prevent communication with the Pulse API.
Error messages:
"The operation "updateOrganizationStatus" is not supported for resource "organizations"!"— indicates a misconfiguration of the operation name; ensure the correct operation is selected.- Errors returned from the API (e.g., 404 Not Found if the organization ID does not exist) should be checked and handled accordingly.
Resolution tips:
- Verify the Organization ID is correct and exists in the Pulse system.
- Confirm that the API key credential has sufficient rights to update organization status.
- Check network connectivity and API endpoint availability.
Links and References
- Pulse API Documentation (hypothetical link)
- n8n documentation on creating custom nodes