Pipelines
Automate document generation by connecting forms to templates
đ Pipelines
Pipelines in Wraft help you automate your document workflows by linking form data with templates. Instead of manually entering information for every document, you can collect responses through forms and have Wraft generate multiple tailored documents in one go.
Overview
Pipelines are especially useful when working with repetitive document types â such as contracts, agreements, or letters â that share a common data source. They simplify document generation by automating the process of creating multiple documents with a single set of data inputs.
âšī¸ Info: Pipelines simplify document generation by automating the process of creating multiple documents with a single set of data inputs.
Creating a Pipeline
To create a new pipeline:
-
Navigate to Pipelines
Go to the Pipelines section from the sidebar
-
Add New Pipeline
Click the Add Pipeline button
-
Configure Pipeline
- Enter a descriptive name for your pipeline (e.g., Sales Contract Workflow)
- Choose your Pipeline Source:
- Wraft Forms (default)
- (External options such as Google Forms, if integrated)
- Select the form you wish to connect to this pipeline
-
Save Pipeline
Click Save to create the pipeline
The pipeline will now appear in your pipeline list and is ready to be configured with steps
âšī¸ Info: The pipeline will now appear in your pipeline list and is ready to be configured with steps.
Configuring Pipeline Steps
Once your pipeline is created, it must be configured to define what documents it will generate and how form fields map to template fields.
Pipeline Management Interface
-
Access Pipeline
Click on the newly created pipeline
-
Understanding Tabs
You'll see three main tabs:
- Steps: Add templates and set up field mappings
- Configure: Modify pipeline settings such as its name or connected form
- Logs: View the execution history of the pipeline
Adding a Pipeline Step
To define the documents that will be generated:
-
Open Steps Tab
Open the Steps tab and click Add Pipeline Step
-
Select Template
A new setup tab will appear:
- Select the Template you want to use for this step
-
Map Fields
After selecting the template, the Mapping Screen will appear:
- Match each template field with the appropriate form field
- Ensure all required fields are correctly mapped to avoid errors
-
Save Step
Click Save to finalize the step
âšī¸ Info: You can repeat this process to add multiple pipeline steps, each linked to a different template â all driven by the same form data.
Running the Pipeline
Once all steps are configured:
-
Locate Pipeline
In the pipeline list, locate your pipeline
-
Execute Pipeline
Click the Run button next to it
-
Fill Form Data
The associated form will appear â fill in the data as required
-
Generate Documents
Click Run to begin the document generation
Wraft will process the form responses and generate one document for each pipeline step, producing fully formatted PDFs for every connected template
Pipeline Management
Tab Reference
- Steps: Configure templates and map data fields
- Configure: Update pipeline metadata such as name or form connection, or delete the pipeline
- Logs: View previous runs, track success/failure, and audit the activity timeline
Monitoring and Maintenance
- Review logs regularly to ensure all runs are successful and error-free
- Test pipelines with sample data before production use
- Update field mappings when templates or forms change
- Archive unused pipelines to keep your workspace organized
Advanced Features
Multiple Template Steps
- Add multiple templates to a single pipeline
- Generate different document types from the same form data
- Each step can use different field mappings as needed
Field Mapping Options
- Direct mapping: Form field directly maps to template field
- Conditional mapping: Map fields based on form responses
- Default values: Set fallback values for optional fields
- Data transformation: Format data during mapping (dates, currency, etc.)
Best Practices
Pipeline Design
- Use clear naming conventions for pipelines and templates to avoid confusion
- Keep field names consistent between forms and templates to simplify mapping
- Document pipeline purposes and use cases for team reference
- Start simple and add complexity gradually
Field Mapping
- Test your mappings with dummy data to ensure all documents generate correctly
- Use descriptive field names that clearly indicate their purpose
- Validate required fields are properly mapped
- Handle optional fields appropriately with defaults or conditions
Process Management
- Monitor logs regularly to ensure all runs are successful and error-free
- Set up error notifications for failed pipeline runs
- Regular testing with updated templates and forms
- Backup important pipelines before making significant changes
Common Use Cases
Client Onboarding
- Collect client information through a single form
- Generate welcome letter, service agreement, and project proposal
- Each document uses relevant portions of the collected data
Employee Management
- New hire form generates multiple HR documents
- Offer letter, employment contract, benefits enrollment
- Consistent data across all employee documentation
Sales Process
- Lead qualification form drives sales documentation
- Proposal, quote, and contract generation
- Streamlined process from lead to signed agreement