PipeRun APIInstall

Summary

Creates a PipeRun activity by sending its type ID, status, and owner ID, with optional activity details and custom request parameters. The request uses the authenticated PipeRun API.

Inputs

• Activity Type Id (required) — Numeric ID of the activity type.
• Status (required) — Numeric activity status: 0 for open, 2 for completed, or 4 for no-show.
• Owner Id (required) — Numeric ID of the user responsible for the activity.
• Additional Parameters — Optional activity fields: deal and requester IDs, title, description, completion comment, video meeting link, duration in minutes, start, delivery and end dates or datetimes, reminders, and associated person or company IDs. Reminders, persons, and companies are JSON values parsed before sending.
• Custom Body Fields — Add key-value fields to the root request body. String values that look like JSON, numbers, or booleans are parsed into those types.
• Custom Body (JSON) — Merge a JSON object into the root request body; matching keys can override existing fields.
• Custom Query Parameters — Add query parameters as key-value pairs.
• Custom Query (JSON) — Merge a JSON object of query parameters; matching keys can override existing parameters.
• Request Options — Configure batching, SSL certificate validation, an HTTP proxy, and request timeout.

Output shape

A response from the PipeRun API for the created activity.

The node sends a POST request to the API using the required PipeRun credentials. The source does not specify the response fields or whether the API returns a single object or another shape.

Links

• n8n community nodes installation guide