Use integration pack nodes

Integration pack nodes appear in the node library alongside built-in nodes. They work exactly like any other node — you drag them onto the canvas, wire their pins, and they execute in the pattern flow. The only additional step is configuring a connection for the pack's service.

Before you begin

• A connection configured for the pack's service (for example, a VirusTotal API key or Jira credentials)

Step 1: Find pack nodes in the node library

Open the node library with Cmd+K (macOS) or Ctrl+K (Windows/Linux). Pack nodes appear under the service name as a category. For example, VirusTotal nodes appear under the VirusTotal category, and Jira nodes appear under the Jira category.

You can also search by node name. Typing "Get IP Report" or "Create Issue" finds the corresponding pack node directly.

Step 2: Add a pack node to the canvas

Select the node to place it on the canvas. Pack nodes appear with execution pins (white triangles on the left and right) and typed data pins for inputs and outputs.

Step 3: Wire the inputs

Wire data to the required input pins. Each input pin has a type (string, integer) and a display name that describes what value is expected. Required pins are marked in the node — the pattern does not compile if a required input is not wired.

For example, the VirusTotal Get IP Report node has one required input: IP Address (string). Wire a string value from an upstream node, a variable, or a literal.

Step 4: Wire the outputs

Connect the output pins to downstream nodes. Pack nodes typically have two types of output:

• Data (object) — the API response body or a nested field from it. Use Get Property nodes to extract specific values.
• Status (integer) — the HTTP status code. Use a Branch node to handle success (200) and error cases (4xx, 5xx) differently.

Step 5: Test the pattern

Select Run in the toolbar and provide test input data. After execution, check the execution log to verify the pack node executed successfully. The log shows the HTTP request details and response data for each pack node.

If the node returns an error status, check the following:

• 401 or 403 — verify your connection credentials are correct
• 404 — verify the input values (for example, the issue key or IP address exists)
• 429 — you hit the API rate limit. Add a delay or reduce the request frequency.

What is next?