Skip to main content

App Info Actions

App actions read the app your API key belongs to and confirm that the 8kit server is answering. They are the quickest way to prove a credential works before the rest of a workflow depends on it.

In n8n they live under the App resource.

Available Operations​

App Actions​

  • Get App Info - Retrieve the app the credential is authenticated as
  • Health Check - Check that the server answers and reports the app healthy

Health Check​

Check that the server answers and reports the app healthy.

Health Check Configuration​

No parameters.

Health Check Response​

{
  "appId": "app123",
  "appName": "my-app",
  "status": "healthy",
  "timestamp": "2024-01-01T10:00:00.000Z"
}

Get App Info​

Retrieve the app the credential is authenticated as.

Get App Info Configuration​

No parameters.

Get App Info Response​

{
  "id": "app123",
  "name": "my-app",
  "description": "Orders and customers sync",
  "createdAt": "2024-01-01T10:00:00.000Z",
  "updatedAt": "2024-01-01T10:00:00.000Z"
}

description is absent when the app has none.

Errors​

If nothing answers at the credential's Host URL, both operations raise:

No 8kit server answered at <Host URL>. Check the Host URL in the credential (it should point at the 8kit service root, e.g. http://8kit:3000).

The Host URL is the service root. The node appends /api/v1/... itself, so do not include the API path in the credential.

With Continue on Fail enabled the item carries an error object with status, message, code and details instead of stopping the workflow.

Next Steps​

Now that you understand all 8kit Node actions:

  1. Explore 8kit Patterns - Learn proven patterns
  2. Try Getting Started - Start using 8kit
  3. Check Admin Dashboard - Monitor your instance