PortaOne icon

PortaOne

Consume PortaOne API (v.1.0.24)

Overview

This node allows you to delete an Account resource in the PortaOne system via its API. It supports both Token and Basic authentication methods. The node is useful for automating account management tasks, such as removing obsolete or deactivated accounts from your PortaOne environment. For example, you might use this node in a workflow that cleans up test accounts after QA runs, or as part of a customer offboarding process.

Properties

Name Meaning
Authentication The authentication method to use. Options: Token Authentication, Basic Authentication.
Account ID The unique ID of the account record to be deleted.
AdditionalFields Optional collection of extra parameters:
- Force: Specifies whether associated non-disconnectable active sessions should be ignored.
- Release Assigned DID: Specifies whether the previously assigned DID number should be released to the pool (true by default).
Simplify Whether to simplify the output data.
SimplifyPath Path to the property that should be returned if simplification is enabled.

Output

  • The node outputs a json field containing the result of the delete operation.
  • If "Simplify" is enabled, only the specified property (via "SimplifyPath") may be returned.
  • The structure of the output will typically include status information about the deletion request, such as success/failure and any relevant messages from the PortaOne API.

Dependencies

  • Requires access to the PortaOne API.
  • Needs either a valid PortaOne Token or Basic authentication credentials configured in n8n.
  • No additional environment variables are required beyond standard n8n credential setup.

Troubleshooting

  • Invalid Credentials: If authentication fails, ensure that the correct credentials are selected and have sufficient permissions.
  • Account Not Found: Deleting a non-existent Account ID will likely result in an error from the API; verify the Account ID before running the node.
  • Active Sessions: If the account has active sessions and "Force" is not set, the deletion may fail. Set "Force" to ignore these sessions if appropriate.
  • DID Release Issues: If "Release Assigned DID" is not set correctly, the associated DID number may not be released as expected.

Common error messages may include:

  • "Authentication failed": Check your credentials and authentication method.
  • "Account not found": Verify the Account ID.
  • "Cannot delete account with active sessions": Consider using the "Force" option.

Links and References

Discussion