Integration Patterns & Recipe Templates

To enable more customers to build medium-complexity integrations independently, we have identified the most common integration patterns and created, for each of them:

• a conceptual implementation guide, and

• a PlanRadar Connect recipe template.

These patterns are based on real customer implementations. They have medium difficulty and require knowledge of how to consume APIs, work with JSON structures, loops, if statements, basic Ruby syntax.

What these integration patterns have in common

Most of these patterns described here:

• are frequently requested by customers

• have been repeatedly and successfully implemented

• are not inherently error-prone when implemented correctly

• are maintainable by non-developers

• provide high value to customers

• scale well across projects

• do not require custom code or infrastructure outside of PlanRadar Connect

Prerequisites and important considerations

Before implementing any of the templates, customers should ensure the following:

Permissions & access

• A dedicated integration user exists

• When creating tickets, all mandatory fields in the form must be supplied in the request.

General Integrations limit: If it does not work in the User Interface, it will not work via APIs either.

Integration patterns

1. Conditional ticket or document creation/update in PlanRadar

Use this pattern when tickets or documents in PlanRadar are created, uploaded or updated automatically when a defined event occurs or a condition is met.

2. Data export to Power BI

Use this pattern when reporting requirements exceed the capabilities of standard PlanRadar Statistics.

3. PDF / Excel / CSV report generation and routing

Use this pattern when reports must be generated automatically, archived, or distributed to external stakeholders.

4. Duration between lifecycle events calculation

Use this pattern when SLA monitoring, resolution time metrics, or response time measurement is required.

5. Field enrichment via lookup table

Use this pattern when ticket data depends on external reference values or manual lookups introduce errors.

6. One-way master data sync into PlanRadar

Use this pattern when project data originates in ERP or CRM and PlanRadar should reflect external updates.

7. Rule-based notifications

Use this pattern when stakeholders require alerts without logging into PlanRadar or escalation workflows are required.

Getting started

For each of the patterns above, we provide a PlanRadar Connect recipe template that you can adapt to your own workflow.

Go to PlanRadar Connect > Library > search for PlanRadar.