Actions118
- Item Actions
- Activity Actions
- Asset Actions
- Authentication Actions
- Collection Actions
- Extension Actions
- Field Actions
- File Actions
- Folder Actions
- Permission Actions
- Preset Actions
- Relation Actions
- Revision Actions
- Role Actions
- Server Actions
- Setting Actions
- User Actions
- Utility Actions
- Webhook Actions
Server → Server Health
AI-generatedOverview
This node performs a health check on a server, typically used to verify if the server is operational and responsive. It is beneficial in monitoring scenarios where you need to ensure the server's availability and status before proceeding with further actions or workflows.
Use Case Examples
- Checking the health status of a Directus server before executing data synchronization.
- Monitoring server uptime and responsiveness in an automated workflow.
Output
JSON
status- The health status of the server, indicating if it is operational.uptime- The duration for which the server has been running without interruption.version- The version of the server software currently running.
Dependencies
- Requires connection to the Directus server, typically authenticated via an API key or token.
Troubleshooting
- If the node fails to connect, verify the server URL and network connectivity.
- Authentication errors may occur if the API key or token is invalid or expired; ensure valid credentials are provided.
- Timeout errors might indicate the server is down or unreachable; check server status manually if needed.
Links
- Directus Server Health API Documentation - Official documentation for the Directus server health endpoint, detailing response structure and usage.