Getting started with PipeLaunch

Getting started

PipeLaunch runs as a panel inside Pipedrive. Open a deal or organisation and the panel appears in the sidebar with your launchers. With one click they send deal data to external systems or open links with Pipedrive fields filled in, without leaving Pipedrive. Everything is managed in Mission Control, opened via the button at the bottom of the panel.

1 · Installing

1. Click Start free in Pipedrive and log in to your Pipedrive account.
2. Grant the requested permissions. They are needed to show the panel and run actions.
3. You are returned to Pipedrive. PipeLaunch now appears as a panel on your deals and organisations.

New installs start automatically on the Free plan: 1 user and up to 5 launchers.

2 · Launchers & Quick Links

PipeLaunch has two kinds, which you combine freely in the panel:

• Launchers 🚀 send deal data to an external system (Make, Zapier, n8n or your own API) and show the result in the panel.
• Quick Links 🔗 open a URL with deal fields filled in automatically. No external connection needed.

3 · Launchers

On click, a launcher sends a request to the Destination URL you set. You decide what goes along and what happens first:

• Payload format: Full sends the complete deal (and optionally its linked person and organisation) plus your launch inputs; Custom sends only the fields you add, under names you choose.
• Launch inputs: Pipedrive fields (loaded live), manual inputs the user fills in at launch time (with a default value, hidden, or required), and layout elements for the launch form.
• Payload Rules: block the launch until the data meets your conditions (e.g. "Deal value must be filled in").
• Headers: add your own HTTP headers (for example an authorisation token). Values are stored encrypted.
• Confirmation dialog & cooldown: optionally show a dialog with your own text before the action runs, and set a wait time between clicks to prevent duplicate triggers.
• Products: include the deal's products, or require them so an automation never runs without line items.

4 · Quick Links

A Quick Link opens a URL with dynamic placeholders. Build the URL with the field picker and PipeLaunch fills the fields in on click:

• For example https://portal.com/customer/{Organization.name} or {Deal.title}.
• Choice and set fields are converted to their readable label, not the internal ID.
• Choose whether the link opens in a new tab or in a pop-up window with custom size and position.

5 · Groups & access

With multiple launchers you keep the panel tidy using groups — drag launchers around in Mission Control and give each group its own color. On top of that, access rules decide who sees which launcher:

• Limit a launcher to a specific pipeline or stage.
• Limit to a user or user group.
• Show a launcher only on deals, persons or organisations.

6 · Launch Feedback

After a click, the result appears as a message in the panel (the ✉ icon next to the launcher). The panel briefly polls for updates, so you also see an asynchronous answer come in.

External systems can also send messages themselves through the feedback API — for example when a process in Make finishes later. Every launch carries a unique event_id; the API is secured with its own API key per account. Optionally, a launcher stays blocked until error messages have been read.

7 · Syncing fields

PipeLaunch syncs the field definitions from your Pipedrive automatically, so choice fields show the right labels and your pipelines and stages match. New or changed fields show up in the field pickers shortly after the change.

8 · Users & seats

On Free, PipeLaunch works with 1 seat and up to 5 launchers. On Team, seats and launchers are unlimited; you manage seats in Mission Control under Users and add or remove colleagues as your team changes.

9 · Billing

• Free is free and has no time limit.
• Team costs €12 per seat per month, or €120 per seat per year (2 months free).
• You choose and change your plan in Mission Control, under Billing.
• All prices are excl. 21% VAT; after each payment you automatically receive an invoice.

The full comparison is on the pricing page.

10 · Security & privacy

• Every request from the panel is verified through the Pipedrive iframe JWT (HS256). Routes are shielded by default (deny-by-default).
• Webhook URLs are validated before sending (SSRF protection), so internal addresses stay unreachable.
• Sensitive values such as OAuth tokens and header values are stored encrypted.
• Every launcher action checks ownership: does the user belong to this account and have the right permissions?
• All data is strictly separated per Pipedrive company (multi-tenant); it is never read across companies.

Support

Questions or need help? Email us at info@cybermatic.nl. We are happy to help with your first launcher or a question about webhooks.