Actions44
- User Actions
- Database Actions
- Collection Actions
- Document Actions
- Index Actions
- Function Actions
- Storage Actions
Overview
This node integrates with the Appwrite API to manage cloud functions within an Appwrite project. Specifically, the "Delete" operation under the "Function" resource allows users to delete a serverless function by its unique identifier. This is useful for cleaning up unused or obsolete functions, managing deployment lifecycle, or automating infrastructure management.
Practical examples include:
- Automatically removing deprecated functions during CI/CD pipelines.
- Cleaning up test functions after automated testing.
- Managing function lifecycle programmatically from n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Function ID | Unique identifier of the function to delete. Can be manually specified or auto-generated. |
Output
The output JSON contains a single field indicating success:
{
"success": true
}
This confirms that the function was successfully deleted. No additional data or binary output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Appwrite API.
- The node depends on the Appwrite client library bundled internally.
- Proper configuration of the Appwrite project and permissions to delete functions is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Function ID will cause an error.
- Insufficient permissions in the Appwrite project may prevent deletion.
- Network or authentication failures can interrupt the API call.
Error messages:
- Errors returned from the Appwrite API typically include details in the response; these are surfaced as node errors.
- If the node fails due to missing credentials, ensure the API key is correctly configured.
- To handle errors gracefully, enable "Continue On Fail" in the node settings.