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 and interact with cloud functions. Specifically, the "List Executions" operation under the "Function" resource retrieves a list of all executions for a given function ID. This is useful for monitoring, debugging, or auditing purposes, allowing users to see past runs of their serverless functions.
Practical examples include:
- Fetching execution logs to analyze function performance.
- Auditing function usage over time.
- Integrating function execution data into dashboards or reports.
Properties
| Name | Meaning |
|---|---|
| Function ID | Unique identifier of the function whose executions you want to list. |
The "Function ID" property is required and can be set manually or auto-generated when creating a new function.
Output
The output is a JSON array containing objects that represent individual function executions. Each object includes details about a single execution instance such as its status, timing, and any returned data or errors.
If the node encounters binary data (not applicable for this operation), it would be included in the binary field, but for listing executions, only JSON data is returned.
Dependencies
- Requires an API key credential for authenticating with the Appwrite API.
- The node depends on the Appwrite client library internally to communicate with the Appwrite backend.
- Proper configuration of the API credentials within n8n is necessary for successful requests.
Troubleshooting
Common issues:
- Invalid or missing Function ID will cause the request to fail.
- Authentication errors if the API key credential is incorrect or expired.
- Network connectivity problems between n8n and the Appwrite server.
Error messages:
- Errors from the Appwrite API are caught and returned with details if available.
- If the node is set to continue on failure, errors are returned as JSON with an error message.
- Typical errors include authorization failures, not found errors if the function ID does not exist, or malformed requests.
Resolutions:
- Verify the Function ID is correct and exists in your Appwrite project.
- Ensure the API key credential is valid and has sufficient permissions.
- Check network connectivity and endpoint URLs.