Studio Project workflows for IP Fabric tables, snapshots, path lookup, and jobs
IP Fabric is a network assurance platform for automated network discovery, inventory, and verification.
This project provides an OpenAPI spec for automating against IP Fabric's REST API via an Integration Model, plus a Studio Project of workflows built on that model.
| Asset | Description |
|---|---|
| OpenAPIs/ | IP Fabric API OpenAPI spec, built from IP Fabric's official Postman collection and API reference docs |
| Studio Projects/ | Itential Platform project containing all 48 workflows in 4 folders |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
IP Fabric API:latest Integration Model | Required to build automation against the OpenAPI spec, and to run the Studio Project below |
Note: This project does not require Itential Gateway. All API calls are made directly from Itential Platform to IP Fabric's REST API.
Import ip_fabric_api-latest.json as an Integration Model in Admin > Integrations, then create an integration pointing at your IP Fabric instance.
Authentication is a static API token in a header:
X-API-Token: <your-ip-fabric-api-token> Generate a token at Settings → API Tokens on your IP Fabric instance.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"apiToken": { "value": "<your-ip-fabric-api-token>" }
},
"server": {
"protocol": "https",
"host": "<your-instance>.ipfabric.io",
"base_path": "/api/v7.8"
}
} Note: IP Fabric doesn't publish a standalone downloadable OpenAPI file — each instance self-generates one from its own backend (reachable at
/api/rapidocon a live instance). Theserversentry in the spec is a static placeholder (https://HOSTNAME/api/v7.8) since Itential Platform Integration Models require a static server URL; the actual host is configured per-instance as shown above.
| Spec | Version | Operations | Description |
|---|---|---|---|
ip_fabric_api-latest.json | latest (curated) | 48 | Built from IP Fabric's official Postman collection and API docs — see breakdown below |
ip_fabric_api-latest.jsonOperations included, by category:
ACI, Addressing, FHRP, Interfaces, Inventory, Management, MPLS, Multicast, Neighbors, Networks, Platforms, QoS, Routing, Security, Spanning Tree, VLAN, VRF, VXLAN, or Wireless — 32 operations across those 19 categoriesBacked by the IP Fabric API:latest Integration Model (see ip_fabric_api-latest.json above). The project contains 48 workflows organized into 4 folders.
| Folder | Workflows | Scope |
|---|---|---|
| Tables | 32 | Query any table across 19 categories (see above) |
| Snapshots | 12 | Snapshot lifecycle management |
| Path Lookup | 1 | Unicast/multicast path simulation |
| Jobs | 3 | Async job control |
The Cancel IP Fabric Job workflow is prefixed to avoid colliding with an identically-named workflow already published for another product — workflow names are unique across the whole Itential Platform instance, not scoped per-project.
| Dependency | Notes |
|---|---|
IP Fabric API:latest Integration Model | Import from ip_fabric_api-latest.json before importing the project |
IP Fabric integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named IP Fabric — update the adapter_id value in each workflow task if yours is named differently |