Appearance
IPinfo
undefined
| Detail | Value |
|---|---|
| Category | Data |
| Base URL | https://ipinfo.io |
| Authentication | Bearer Token |
| Endpoints | 7 |
| Connector key | ipinfo |
Using IPinfo in a workflow
- Go to Connections and click New Connection.
- Pick IPinfo 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 | 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
| Detail | Value |
|---|---|
| Operation ID | ip_details_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your IPinfo connection from the Connection dropdown.
- In the Operation dropdown, select
ip_details_0. - 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
| Detail | Value |
|---|---|
| Operation ID | geolocation_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your IPinfo connection from the Connection dropdown.
- In the Operation dropdown, select
geolocation_1. - 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
| Detail | Value |
|---|---|
| Operation ID | organization_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your IPinfo connection from the Connection dropdown.
- In the Operation dropdown, select
organization_2. - 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
| Detail | Value |
|---|---|
| Operation ID | company_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your IPinfo connection from the Connection dropdown.
- In the Operation dropdown, select
company_3. - 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
| Detail | Value |
|---|---|
| Operation ID | privacy_detection_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your IPinfo connection from the Connection dropdown.
- In the Operation dropdown, select
privacy_detection_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
| Detail | Value |
|---|---|
| Operation ID | abuse_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your IPinfo connection from the Connection dropdown.
- In the Operation dropdown, select
abuse_5. - 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
| Detail | Value |
|---|---|
| Operation ID | domains_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your IPinfo connection from the Connection dropdown.
- In the Operation dropdown, select
domains_6. - 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.