Debugging actions¶

While you’re developing actions for your application, you may want to debug the webhook configured for the action. To do so, start the server in debugging mode. In the case of errors, the GraphQL response contains debugging information of webhook calls in the extensions.internal field.

For example, let’s consider the following mutation:

mutation {
  create_user(email: "foo@bar.com", name: "Foo"){
    id
    user {
      name
      email
      is_admin
    }
  }
}

In case of errors, the response will look like the following if the debugging mode is enabled.

{
  "errors": [
    {
      "extensions": {
        "internal": {
          "response": {
            "status": 200,
            "body": "some-string",
            "headers": [
              {
                "value": "application/json",
                "name": "Content-Type"
              }
            ]
          },
          "request": {
            "body": {
              "session_variables": {
                "x-hasura-role": "admin"
              },
              "input": {
                "email": "foo@boo.com",
                "name": "Foo"
              },
              "action": {
                "name": "create_user"
              }
            },
            "url": "http://127.0.0.1:5593/invalid-response",
            "headers": [

            ]
          },
          "error": "expecting object or array of objects for action webhook response"
        },
        "path": "$",
        "code": "parse-failed"
      },
      "message": "expecting object or array of objects for action webhook response"
    }
  ]
}

« previous | next »

Was this page helpful?

Want to contribute or report missing content?

edit this page on github | contributing guidelines | report an issue

Hasura GraphQL engine is open source. See license