# Integrating Formize with Low‑Code Platforms for Rapid Business Process Automation

Enterprises today demand speed, flexibility and compliance when digitizing manual processes. Traditional software development cycles often clash with the need to roll out new forms, approvals and data collection mechanisms within weeks. Low‑code platforms such as **Microsoft Power Apps**, **OutSystems**, **Mendix** and **AppSheet** promise drag‑and‑drop UI creation, visual workflow orchestration and instant deployment. Yet, many low‑code solutions still lack a native, fully featured PDF form engine—something critical for legal, tax, HR and regulated industries.

**Formize** bridges that gap. Its four core products—Web Forms, Online PDF Forms, PDF Form Filler and PDF Form Editor—deliver a complete digital lifecycle for static documents and dynamic web‑based questionnaires. By exposing RESTful APIs, webhook events and embeddable iFrames, Formize can be consumed by any low‑code canvas without writing a single line of code.

In this guide we will:

1. Outline the technical fit between Formize and low‑code platforms.  
2. Walk through a step‑by‑step integration that creates a fully automated vendor onboarding workflow.  
3. Highlight best practices for data validation, security, version control and analytics.  
4. Discuss future trends such as AI‑enhanced field extraction and multi‑language consent handling.

Let’s dive in.

---

## 1. Why Combine Formize with Low‑Code?

| Benefit | Traditional Coding | Low‑Code + Formize |
|---------|-------------------|--------------------|
| Time to market | Months of development, testing and deployment | Days to weeks because UI, logic and forms are pre‑built |
| Form capabilities | Custom PDF generation libraries require expertise | Ready‑made fillable PDFs, conditional logic and electronic signatures |
| Compliance | Manual audit of data handling | Built‑in audit trail, **[GDPR](https://gdpr.eu/)**‑ready storage, **[SOC 2](https://secureframe.com/hub/soc-2/what-is-soc-2)** certification |
| Scalability | Requires custom scaling logic | Cloud‑native Formize scales automatically, low‑code platforms handle horizontal scaling |
| Maintenance | Codebase grows, technical debt accumulates | Visual workflows can be updated by citizen developers |

The synergy is especially powerful when an organization must collect **legally binding PDFs** (e.g., contracts, tax forms) alongside **dynamic web questionnaires** (e.g., risk assessments). Formize handles the PDF side, while the low‑code platform coordinates the overall process flow, notifications and downstream integrations (ERP, CRM, DMS).

---

## 2. Core Formize APIs Relevant to Low‑Code Integration

Formize offers three primary integration mechanisms:

1. **REST API** – Create, retrieve, update and delete form templates, submissions and metadata.  
2. **Webhooks** – Event‑driven notifications for form submission, status change, field validation errors, etc.  
3. **Embedded iFrame** – Directly embed a web form or PDF filler/editor into a low‑code screen with a simple URL and authentication token.

Typical API endpoints (illustrative, not exhaustive):

```http
GET /api/v2/forms/{formId}
POST /api/v2/forms/{formId}/submissions
GET /api/v2/submissions/{submissionId}
POST /api/v2/webhooks
```

All calls require an **API key** scoped to the organization and support **OAuth 2.0** for token exchange. Responses are JSON, making them trivial to consume in any low‑code data connector.

---

## 3. Designing a Vendor Onboarding Workflow

Below is a concrete example that shows how a procurement team can automate vendor onboarding from start to finish using **Microsoft Power Apps** (as the low‑code host) and **Formize** (as the form engine).

### 3.1 High‑Level Flow

```mermaid
flowchart TD
    A["Start: Procurement staff opens Vendor Onboarding app"] --> B["Select ‘Create New Vendor’ button"]
    B --> C["Power Apps triggers Formize Web Form creation via API"]
    C --> D["Embedded Formize Web Form displayed to vendor"]
    D --> E["Vendor fills questionnaire, uploads required documents"]
    E --> F["Formize emits ‘submission.completed’ webhook"]
    F --> G["Power Automate picks up webhook, validates data"]
    G --> H["If validation passes → Create vendor record in ERP"]
    G --> I["If validation fails → Send error email to vendor"]
    H --> J["Generate PDF contract using Formize PDF Form Editor"]
    J --> K["Vendor signs contract using PDF Form Filler (embedded)"]
    K --> L["Signed PDF stored in DMS, status updated in Power Apps"]
    L --> M["Procurement receives notification, closes onboarding"]
```

### 3.2 Step‑by‑Step Implementation

#### Step 1 – Create a Power Apps Canvas App
* Drag a **Button** onto the screen labelled *Create New Vendor*.
* Add a **Data source** using the **Custom connector** feature that points to Formize’s REST API (import the OpenAPI spec provided by Formize).

#### Step 2 – Generate a Unique Form Instance
* On the button’s *OnSelect* property, call the API:  

```powerapps
Set(varFormId, "vendor_onboard_" & GUID());               // unique identifier
Set(varCreateResponse,
    Formize.CreateFormInstance({
        templateId: "TEMPLATE_VENDOR_ONBOARD",
        instanceId: varFormId,
        metadata: {
            requester: User().Email,
            createdAt: Now()
        }
    })
);
```

* Store the returned `instanceId` for later use.

#### Step 3 – Embed the Formize Web Form
* Insert an **iFrame** control (available via the **HTML Text** component).  
* Set its `HTMLText` property to:

```html
<iframe src="https://app.formize.com/embed/{varFormId}?auth={YourAuthToken}"
        width="100%" height="800px" frameborder="0">
</iframe>
```

* The `auth` token can be generated on‑the‑fly with a Power Automate **HTTP** action that calls Formize’s OAuth token endpoint.

#### Step 4 – Listen for the Submission Webhook
* In **Power Automate**, create a **When a HTTP request is received** trigger.  
* Configure Formize to post to this endpoint by calling `POST /api/v2/webhooks`:

```json
{
  "url": "https://<your‑flow>.flow.microsoft.com/api/webhooks/incoming",
  "events": ["submission.completed"],
  "filters": {
    "formId": varFormId
  }
}
```

* The flow extracts the payload, validates required fields (e.g., tax ID, insurance docs) and writes the data to the ERP system via its connector.

#### Step 5 – Conditional Branching
* **Success branch** – Use the **Create record** action in the ERP connector, then call Formize’s PDF Form Editor API to generate a contract PDF pre‑filled with vendor