Port

Describe the user, which organization he is connected to and what teams he is a member of and more information regarding the user. Can be useful for questions that relate to the user or when looking up for related entities to the user

List actions in your organization.

Without identifiers: Returns summary list (identifier, title, description, trigger type).

With identifiers: Returns full action details including complete input schemas.

Use full details when you need the input schema before running an action.

List blueprints in your organization.

Without identifiers: Returns summary list (identifier, title, description, property/relation names).

With identifiers: Returns full blueprint details including property definitions, schemas, relations, and enum values.

Use full details when you need:

• Property types for constructing filters

• Enum values for properties

• Relation target blueprints

Query entities from a blueprint. All parameters are composable.

FILTERING:

• identifiers: Pre-select specific entities by ID

• query: Apply filter rules (can combine with identifiers)

OUTPUT OPTIONS (composable):

• groupBy: Get value distribution grouped by property/relation/scorecard

• countOnly: Include total count in response

• Can request multiple: e.g., groupBy + countOnly returns both groups and total count

RESPONSE includes:

• entities + hasMoreEntities: when listing (no groupBy)

• groups + hasMoreGroups: when groupBy is set

• count: when countOnly is true

⚠️ CALL list_blueprints FIRST if filtering by blueprint-specific properties/relations to understand:

1. PROPERTY TYPES: string, number, date, boolean, array - determines valid operators

2. ENUM VALUES: Check schema.properties.{field}.enum for exact values

3. RELATION TARGETS: Check relations.{name}.target for valid entity identifiers

❌ COMMON FAILURES:

• Wrong enum value casing (e.g., "open" instead of "Open")

• Wrong relation target (using service ID for a _user relation)

• Wrong operator for type (e.g., "contains" on non-array)

INCLUDE PARAMETER:

• Use specific identifiers: "status", "assignee", "security-maturity"

• NOT categories: "properties", "relations", "scorecards"

SEARCHING BY NAME:

• Use "contains" on BOTH $identifier AND $title with "or" combinator

• Use single words (e.g., "payment" not "payment gateway")

DATE FILTERING:

• Range: { "property": "created_at", "operator": "between", "value": { "from": "ISO_DATE", "to": "ISO_DATE" } }

• Comparison: { "property": "created_at", "operator": ">=", "value": "ISO_DATE" }

USER IDENTIFIERS:

• _user blueprint uses EMAIL as identifier

• Filter by user: { "relation": "creator", "operator": "=", "value": "john@company.com" }

FILTERING BY RELATIONS:

• Use "relation" key, NOT "property": { "relation": "assignee", "operator": "=", "value": "..." }

• Single relations: use "="

• Array relations: use "contains" or "containsAny"

SORTING:

• Use "order": "asc" or "desc" (NOT "direction")

List scorecards in your organization.

Without identifiers: Returns summary list (identifier, title, blueprint, levels, compacted rules).

With identifiers: Returns full scorecard details including complete rule configurations.

Load specialized guidance for a domain-specific task.

Skills provide step-by-step instructions for common workflows. Load a skill BEFORE starting a specialized task to ensure consistent, thorough handling.

Available Skills:

• troubleshoot-integration: Diagnose and resolve integration sync issues, mapping errors, and data problems. Use when users report missing data, sync failures, or integration errors.

Usage:

• load_skill({ name: "skill-name" }) → Returns main instructions + list of available resources

• load_skill({ name: "skill-name", resource: "references/REFERENCE.md" }) → Returns specific resource content

Run an action by its identifier.

DISCOVERY WORKFLOW:

1. Use list_actions tool to discover all available actions and their identifiers

2. Use get_action tool with the specific action identifier to get:

   • The exact action definition

   • Required input properties and their schemas

   • Whether entityIdentifier is required (check trigger.operation and trigger.blueprintIdentifier)

   • Property types, formats, constraints, and required fields

3. Format the properties object according to the action's trigger.userInputs.properties schema

4. Call run_action with the actionIdentifier, properties, and optionally entityIdentifier

ENTITY IDENTIFIER REQUIREMENTS:

• REQUIRED for DAY-2 and DELETE operations when trigger.blueprintIdentifier exists

• The entityIdentifier must be a valid entity identifier from the blueprint specified in trigger.blueprintIdentifier

• To find valid entity identifiers, use list_entities tool with the blueprint identifier from trigger.blueprintIdentifier

• NOT needed for CREATE operations or global actions (when trigger.blueprintIdentifier is undefined)

• Use get_action to determine if entityIdentifier is required for a specific action by checking:

  • trigger.operation: must be "DAY-2" or "DELETE"

  • trigger.blueprintIdentifier: must exist (not undefined)

PROPERTY FORMATTING:

• Always check get_action response for the exact property schema

• Match property types, formats, and constraints exactly as defined

• Include all required properties as specified in trigger.userInputs.required

Perform semantic retrieval over the documentation and other knowledge sources of Port and return the most relevant chunks for a given query. A "chunk" is a short, self-contained snippet of text taken from a single page or item within these sources (for example, part of a documentation page) and includes its source URL and markdown content. Chunks are returned in descending order of relevance to the query, and the tool always returns a fixed number of chunks (top-k). If the knowledge sources do not contain information relevant to the query, the returned chunks may be only weakly related or entirely unrelated. Use this tool anytime you need information about Port.

Track action execution status