Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
This node provides integration with the GateKit universal messaging gateway API, allowing users to manage various resources such as projects, API keys, identities, members, messages, platforms, platform logs, and webhooks. Specifically, for the Projects resource and the Delete operation, this node enables deleting an existing project by its identifier.
Use cases include automating project lifecycle management within GateKit, such as cleaning up unused or obsolete projects programmatically from workflows. For example, after archiving data related to a project, you can use this node to delete the project to keep your workspace organized.
Properties
| Name | Meaning |
|---|---|
| Project | Project identifier to operate on (string). This specifies which project will be deleted. |
Output
The output of the node corresponds to the response from the GateKit API when deleting a project. Typically, this would be a JSON object indicating success or failure of the deletion request. The exact structure depends on the API but usually includes status information and possibly metadata about the deleted project.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the GateKit API.
- The node uses the base URL provided by the API credentials configuration.
- The HTTP method used is DELETE on the endpoint
/api/v1/projects/{project}where{project}is the project identifier.
Troubleshooting
Common issues:
- Attempting to delete a non-existent project will likely result in an error response from the API.
- Insufficient permissions or invalid API credentials may cause authorization errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- 404 Not Found: The specified project does not exist. Verify the project identifier.
- 401 Unauthorized or 403 Forbidden: Authentication failed or user lacks permission. Check API key validity and access rights.
- 400 Bad Request: Invalid parameters passed. Ensure the project identifier is correctly formatted.
Resolution tips:
- Confirm the project ID is correct and exists.
- Verify that the API key credential is valid and has sufficient permissions.
- Check network connectivity and API endpoint accessibility.
Links and References
- GateKit API Documentation (general reference for API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes