Managing a construction project involves many tools, teams, and tasks. But switching between platforms like Procore, spreadsheets, and emails can lead to confusion, delays, and missed information.
Let's show you how you can set up a workflow where records from Procore automatically create tasks inside Jugl, so your team can track, manage, and act faster, all from one place.
This integration helps turn Procore activity (like new records or updates) into organized, trackable work in Jugl. No more manual entries. No more lost documents or delays.
We’ll walk through how to:
Set up Procore inside Jugl (using connectors)
Choose the right triggers
Connect your account
Build a recipe to create a Jugl task when something happens in Procore
Use real construction scenarios (like trucking tickets and RFIs)
Plan simple diagrams (you can design visually based on our cues)
Start by Selecting Procore as the Source App
Image A: Choose Procore as Your Source Application
You begin by selecting the Procore app from your available applications. This is where the automation will listen for changes. Procore becomes your source, the system where the action begins.
When you select Procore:
You will be prompted to authenticate it (via API key or OAuth)
Make sure the account you’re connecting has access to the project you’re working on
Select the workspace or location for the automation (e.g., Templates)
You should now see Procore listed as the active app.
Choose a Trigger: What Should Start the Automation?
Image B: Pick When the Workflow Should Start
Next, define when the workflow should run. You’ll see a list of possible triggers.
For example:
New record in Procore – starts when a new item is created (like an RFI)
New or updated record – covers both creation and modification
New event – broader trigger for different types of changes
In most cases for construction tracking, “New or updated record” works best. That way, both new entries and important changes trigger your automation.
Choose this trigger and move forward.
Set Up the Connection to Procore
Image C: Set Up the Connection Between Procore and Jugl
Now it's time to connect your Procore account. You’ll need:
A Connection name (e.g., “My Procore Project”)
The right location (like “Templates” or “Main Automation”)
Authentication (usually OAuth 2.0 or a secure API token)
Your Procore project URL (formatted like https://yourcompany.procore.com)
Once you connect, you’ll be able to pull data from any permitted projects.
👉 Note: Make sure the Procore user has the right permissions for viewing or editing the data.
Now Build the Automation Recipe
Image D: Visual Flow: Turning Procore Changes into Jugl Tasks
Now that you’ve connected Procore, it’s time to build the automation or recipe. In Jugl, recipes are step-by-step instructions. Here's how a basic recipe would work:
Trigger: Procore record created or updated
Monitor: Check the task creation step for errors
Action: Create a new task in Jugl
Retry: If failed, try again
Stop: If still fails, log the error and stop
Inside Jugl:
Choose the board where you want the task to appear (e.g., “Construction Tickets”)
Set the task name (you can pull values from the Procore record, like RFI title or task ID)
Add a description with more Procore info
Set priority, labels, and assignees as needed
Use Case 1: Automating Trucking Tickets for Faster Jobsite Entry
One of the pain points discussed in the meeting was the manual handling of trucking tickets. Right now, someone takes a photo, sends it via text or email, and then someone else enters the data into Procore or a spreadsheet. That leads to lost documents and delays.
How the flow works:
A new ticket image or record is uploaded in Procore (from a mobile device)
Trigger fires and sends the info to Jugl
Jugl creates a task titled “New Truck Ticket – Site A”
The image and ticket details are added in the task
A supervisor is automatically assigned to review
Step | What Happens | System |
Driver uploads ticket | Record created in Procore | Procore |
Automation fires | Checks for new ticket | Jugl |
Task created | Ticket details shown | Jugl |
Team notified | Supervisor checks & approves | Jugl |
👉 This replaces long chains of messages with one organized task.
Use Case 2: RFIs to Task Boards
RFIs (Request for Information) often cause delays if not tracked properly. With this setup:
When a new RFI is created in Procore, Jugl auto-creates a task
The RFI question, due date, and reference number are pre-filled
Assignee is based on the Procore field engineer
This ensures RFIs are not just buried in email, they become active tasks with visibility.
Step | What Happens |
New RFI in Procore | Trigger fires |
Jugl task created | Title: “RFI #1202 – Plumbing” |
Assigned to | Site engineer |
Status | “Pending Response” |
Use Case 3: Submittals and Change Orders
Submittals and change orders can get lost if not followed up.
With this automation:
Procore submittals automatically create a task in Jugl
The document and due date are included
If it’s a change request, it’s labeled “Urgent” and assigned to a project lead
This ensures important approvals don’t get delayed.
Item | Triggered in | Tracked in |
Submittal | Procore | Jugl Task |
Change Order | Procore | Jugl Task with urgency tag |
Making the Workflow Better with AI and Mobile
In the meeting, AI features and mobile tracking were discussed. Jugl’s vision includes:
Using AI to extract data from images (like dump tickets)
Creating tasks automatically based on scanned content
Letting field users submit info via mobile forms
Tracking user location for task context (optional)
This means drivers or crew members can:
Submit info directly
Attach files or images
See their assigned tasks on mobile
No training required, just tap and go.
Notes and Best Practices
Keep your Procore records consistent. If naming is messy, Jugl task titles will be too.
Don’t overwhelm teams with too many triggers. Use filters.
Test on a small project first. Try trucking tickets or RFIs to see real impact.
Use labels and tags in Jugl for sorting and dashboards.
You can later expand this flow to include HR, equipment logs, or payment approvals.
Final Note
This setup helps construction teams stay on top of important project data without switching tools or missing deadlines. Procore becomes the data source. Jugl becomes the command center. Field teams stay informed. Office staff stay organized.