Skip to main content

Automated workorder to task creation with Mailparser / Docparser

Teresa Bui avatar
Written by Teresa Bui
Updated over 2 weeks ago

Automate Task Creation with Mailparser and Docparser

What you'll learn: This guide shows you how to automatically create tasks in Uptick from work orders sent via email or PDF documents using Mailparser and Docparser integrations.


Overview

If you receive automated work orders from clients, you can streamline your workflow by automatically converting them into Uptick tasks. This integration uses third-party services—Mailparser for emails and Docparser for PDF documents—to extract data and create tasks without manual entry.

Before you begin:

  • This setup is designed for advanced technical users

  • You'll need an active Mailparser or Docparser account

  • Contact our support team if you need assistance with configuration

Learn more about these services:


Create Tasks from Email Work Orders

Step 1: Set up your Mailparser account

If you don't already have a Mailparser account, sign up at mailparser.io.

Step 2: Create an inbox and scan emails

  1. Sign in to Mailparser and create a new inbox

  2. Note the unique email address generated—this is where work order emails will be sent

  3. Forward at least 2 sample work order emails to this address (Mailparser uses these to analyze patterns and suggest parsing rules)

  4. Once Mailparser receives the emails, click Add some parsing rules

  5. Review the suggested rules and click OK, start with this to accept them as a starting point

Tip: You can customize rules later by clicking Rules from the side menu to define specific text filters and email regions.

Step 3: Configure the Uptick integration

  1. In your Mailparser inbox, navigate to Integrations > Add new integration > Generic Webhook

  2. Enter a name for the integration

  3. Set the payload method to JSON

  4. In the Target URL field, enter:

https://servername.onuptick.com/api/v2/tasks/mailparser_webhook

Replace servername with your Uptick server address (the first part of your Uptick URL)

  1. Under Advanced Options, configure the following settings:

Setting

Value

HTTP Verb

POST

Repeating Data Behaviour

One request per email

Data structure

Custom - provide your own template

Structure template

Map Uptick task fields to the parsing rules you created in Mailparser

Additional Headers

Add your authorization key (see instructions below)

Step 4: Generate your authorization key

  1. Create a username and password specifically for this integration (this is separate from your other account credentials)

  2. Copy the generated authorization key

  3. Paste it into the Additional Headers field in Mailparser

  4. Important: Send this authorization key to our support team so they can add it to your server configuration

Step 5: Test the integration

  1. Click Save & Test to verify the integration works correctly

  2. If tasks aren't being created, check the error logs in Mailparser to troubleshoot

Note: All errors are recorded in Mailparser's logs, which you can use to identify and resolve any issues.


Create Tasks from PDF Work Orders

Overview

The Docparser integration works similarly to Mailparser but extracts data from PDF documents instead of emails. It can identify repeating text patterns and tables to automatically populate task information.

Setup process

The configuration steps for Docparser follow the same pattern as the Mailparser setup:

  1. Create a Docparser account at docparser.com

  2. Upload sample PDF work orders to train the parser

  3. Configure parsing rules to extract relevant data

  4. Set up the webhook integration with Uptick

  5. Generate and configure your authorization key

  6. Test the integration

For detailed configuration steps, refer to the Mailparser instructions above and adapt them for Docparser, or contact our support team for assistance.


Need Help?

If you encounter any issues or need assistance with setup, please contact our support team. For additional information about Mailparser and Docparser features, refer to their respective support documentation.

Did this answer your question?