SharePoint-Powered Procore Automator

Procore Project Sequence ID Integration via Power Apps in Teams (SharePoint List Storage)

Overview

We are seeking a Power Platform developer to build a Project Sequence ID automation that integrates with Procore, using Power Apps inside Microsoft Teams as the user interface. The solution will generate a unique, sequential Project ID and sync it to Procore’s Project Number field. All sequence tracking and configuration will be stored in SharePoint Lists.

Objective

Develop a Teams‑embedded Power App and Power Automate flows that:

• Generate a unique, sequential Project ID based on our business rules.
• Store and manage sequence logic in SharePoint Lists.
• Push the generated ID into Procore via API.
• Provide a simple Teams‑based interface for project creation and review.


---

Key Requirements

1. Power Apps (Teams Embedded)

• Build a Canvas Power App that runs directly inside Microsoft Teams.
• App capabilities:• Capture project details (region, year, project name, etc.).
• Display the generated Project Sequence ID.
• Trigger the automation flow to create/update the project in Procore.

• UI must be clean, intuitive, and optimized for Teams users.


2. Power Automate Integration

• Create flows that:• Generate the next sequential Project ID.
• Read/write sequence data from SharePoint Lists.
• Call Procore’s API using HTTP actions or a custom connector.
• Handle OAuth2 authentication securely.
• Log errors and notify users of failures.


3. Procore API Integration

• Experience building custom connectors or using HTTP actions in Power Automate.
• Ability to:• Authenticate with Procore.
• Write to the Project Number field.
• Optionally read project metadata or trigger updates.


4. Sequence ID Logic

• Build a rules‑based ID generator using:• Year
• Region / Business Unit
• Incremental sequence number

• Requirements:• No duplicates
• Concurrency‑safe logic (e.g., locking or controlled updates)
• Easy to modify rules in the future


5. SharePoint List Storage (Preferred)

• Use SharePoint Lists to store:• Last used sequence number per region/year
• Region mappings
• Audit history of generated IDs
• Configuration settings

• Must be structured for easy admin updates.


6. Security & Governance

• Follow Power Platform and Teams governance best practices.
• Store API keys and secrets securely (e.g., environment variables, Azure Key Vault if needed).
• Ensure proper permissions for SharePoint and Teams integration.


7. Documentation & Handover

• Provide:• Solution architecture
• Setup and deployment instructions
• Admin guide for modifying sequence rules
• User guide for Teams users

---

Deliverables

• Fully functional Power App embedded in Teams.
• Power Automate flows for ID generation and Procore sync.
• Custom connector (if required) for Procore API.
• SharePoint Lists for sequence tracking and configuration.
• Complete documentation and source files.

---

Required Skills

• Power Apps (Canvas apps)
• Power Automate (HTTP actions, custom connectors)
• SharePoint Lists (data modeling, permissions)
• REST API integration with OAuth2
• Experience with Procore API is a strong advantage


---

Nice-to-Have Skills

• Construction industry workflow familiarity
• Teams app deployment experience
• Ability to optimize SharePoint for performance and concurrency


---

What to Include in Your Proposal

• Examples of Power Apps + API integration projects
• Experience with Procore or similar platforms
• Proposed architecture (SharePoint list structure, flow design)
• Estimated timeline and cost
• Any questions about our ID format or workflows