Skip to content
For LLMsView as Markdown·

IPinfo ​

undefined

DetailValue
CategoryData
Base URLhttps://ipinfo.io
AuthenticationBearer Token
Endpoints7
Connector keyipinfo

Using IPinfo in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick IPinfo from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
GET IP Details
GET Geolocation
GET Organization
GET Company
GET Privacy Detection
GET Abuse
GET Domains

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET ​

IP Details

DetailValue
Operation IDip_details_0
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your IPinfo connection from the Connection dropdown.
  3. In the Operation dropdown, select ip_details_0.
  4. 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 IPinfo API reference.

GET ​

Geolocation

DetailValue
Operation IDgeolocation_1
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your IPinfo connection from the Connection dropdown.
  3. In the Operation dropdown, select geolocation_1.
  4. 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 IPinfo API reference.

GET ​

Organization

DetailValue
Operation IDorganization_2
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your IPinfo connection from the Connection dropdown.
  3. In the Operation dropdown, select organization_2.
  4. 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 IPinfo API reference.

GET ​

Company

DetailValue
Operation IDcompany_3
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your IPinfo connection from the Connection dropdown.
  3. In the Operation dropdown, select company_3.
  4. 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 IPinfo API reference.

GET ​

Privacy Detection

DetailValue
Operation IDprivacy_detection_4
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your IPinfo connection from the Connection dropdown.
  3. In the Operation dropdown, select privacy_detection_4.
  4. 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 IPinfo API reference.

GET ​

Abuse

DetailValue
Operation IDabuse_5
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your IPinfo connection from the Connection dropdown.
  3. In the Operation dropdown, select abuse_5.
  4. 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 IPinfo API reference.

GET ​

Domains

DetailValue
Operation IDdomains_6
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your IPinfo connection from the Connection dropdown.
  3. In the Operation dropdown, select domains_6.
  4. 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 IPinfo API reference.