Appearance
Cat Facts
Free API serving random cat facts. Great for testing simple GET requests.
| Detail | Value |
|---|---|
| Category | Testing |
| Base URL | https://catfact.ninja |
| Authentication | None |
| Endpoints | 3 |
| Connector key | catfact |
Using Cat Facts in a workflow
- Go to Connections and click New Connection.
- Pick Cat Facts from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /fact | Get a random cat fact |
GET /facts | Get a list of cat facts |
GET /breeds | Get a list of cat breeds |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /fact
Get a random cat fact
| Detail | Value |
|---|---|
| Operation ID | test.getFact |
| Method | GET |
| Path | /fact |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Cat Facts connection from the Connection dropdown.
- In the Operation dropdown, select
test.getFact. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cat Facts API reference.
GET /facts
Get a list of cat facts
| Detail | Value |
|---|---|
| Operation ID | test.listFacts |
| Method | GET |
| Path | /facts |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
limit | query | integer | No |
page | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Cat Facts connection from the Connection dropdown.
- In the Operation dropdown, select
test.listFacts. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cat Facts API reference.
GET /breeds
Get a list of cat breeds
| Detail | Value |
|---|---|
| Operation ID | test.listBreeds |
| Method | GET |
| Path | /breeds |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
limit | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Cat Facts connection from the Connection dropdown.
- In the Operation dropdown, select
test.listBreeds. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Cat Facts API reference.