Procore: what the assistant can do
Everything the assistant can do in Procore by text: 8 actions, with example texts, the Procore API call behind each one, and which ones ask first or can be undone.
In Procore, the assistant can log crew hours, add a daily log note, log a delay, add photos, add a punch item, log an observation, check open RFIs and check the schedule. You ask by text, in your own words.
Status: Built, not open yet. How to connect, permissions and limits: Procore.
| What it does | Asks first? | Undo |
|---|---|---|
| Log crew hours | If unsure | 10 minutes |
| Add a daily log note | If unsure | 10 minutes |
| Log a delay | If unsure | 10 minutes |
| Add photos | If unsure | 10 minutes |
| Add a punch item | If unsure | 10 minutes |
| Log an observation | If unsure | 10 minutes |
| Check open RFIs | No | – |
| Check the schedule | No | – |
Asking first and undo follow the same rules for every tool: see Confirmations and undo.
Log crew hours
Section titled “Log crew hours”Adds a manpower entry to the project’s daily log: how many workers, hours each, the subcontractor if you name one, and what they did.
- Asks before doing it? Usually not. It asks first if it isn’t sure what you meant, a name only roughly matches, or the request covers more than 5 records.
- Can be undone? Yes. Text “undo” within 10 minutes.
- Procore API call:
POST /rest/v1.0/projects/{project_id}/manpower_logs - Action name:
procore.log_manpower
Example texts:
- “Finished framing at 12 Oak, 4 guys 8 hours”
- “Smith Framing had 6 guys at the Lopez job today, 7.5 hrs”
- “3 trabajadores 8 horas en 12 Oak, terminamos el drywall”
Add a daily log note
Section titled “Add a daily log note”Adds a note to the project’s daily log: inspections, deliveries, visitors, anything that happened on site.
- Asks before doing it? Usually not. It asks first if it isn’t sure what you meant, a name only roughly matches, or the request covers more than 5 records.
- Can be undone? Yes. Text “undo” within 10 minutes.
- Procore API call:
POST /rest/v1.0/projects/{project_id}/notes_logs - Action name:
procore.add_daily_note
Example texts:
- “daily log for 12 Oak: inspector passed the rough electrical”
- “Smith job, drywall delivered this morning, stacked in garage”
Log a delay
Section titled “Log a delay”Adds a delay to the project’s daily log, matched to your delay types (rain becomes Weather), with the hours lost if you say.
- Asks before doing it? Usually not. It asks first if it isn’t sure what you meant, a name only roughly matches, or the request covers more than 5 records.
- Can be undone? Yes. Text “undo” within 10 minutes.
- Procore API call:
POST /rest/v1.0/projects/{project_id}/delay_logs - Action name:
procore.log_delay
Example texts:
- “log rain delay today at the Smith job”
- “lost 3 hours at 12 Oak waiting on the inspector”
- “retraso por lluvia hoy en el trabajo de Smith”
Add photos
Section titled “Add photos”Uploads the photos you text to the project’s Photos, with a description and into an album if you name one (a new album is created).
- Asks before doing it? Usually not. It asks first if it isn’t sure what you meant, a name only roughly matches, or the request covers more than 5 records.
- Can be undone? Yes. Text “undo” within 10 minutes.
- Procore API call:
POST /rest/v1.0/images?project_id={id} - Action name:
procore.add_photos
Example texts:
- “[3 photos] add these to 12 Oak”
- “[2 photos] 12 Oak framing, put them in the Framing album”
Add a punch item
Section titled “Add a punch item”Creates a punch list item on the project, assigned to the person you name (from the project’s assignee list) and with a due date if you give one.
- Asks before doing it? Usually not. It asks first if it isn’t sure what you meant, a name only roughly matches, or the request covers more than 5 records.
- Can be undone? Yes. Text “undo” within 10 minutes.
- Procore API call:
POST /rest/v1.1/punch_items - Action name:
procore.create_punch_item
Example texts:
- “punch item at 12 Oak: cracked tile in master bath, assign Mike”
- “add to the Smith punch list: touch up paint in hallway, due Friday”
- “punch item en 12 Oak: falta la tapa del contacto en la cocina”
Log an observation
Section titled “Log an observation”Logs a safety, quality or other observation on the project, using your project’s observation types, assigned to someone if you say.
- Asks before doing it? Usually not. It asks first if it isn’t sure what you meant, a name only roughly matches, or the request covers more than 5 records.
- Can be undone? Yes. Text “undo” within 10 minutes.
- Procore API call:
POST /rest/v1.0/observations/items - Action name:
procore.create_observation
Example texts:
- “observation: missing guardrail on 2nd floor at 12 Oak”
- “safety observation at the Smith job, no hard hats on the roofers, assign Dana”
Check open RFIs
Section titled “Check open RFIs”Lists the project’s open RFIs, soonest due first, with overdue ones flagged and who has the ball.
- Asks before doing it? No. It only looks things up.
- Can be undone? Nothing to undo: it doesn’t change anything.
- Procore API call:
GET /rest/v1.0/projects/{project_id}/rfis - Action name:
procore.list_rfis
Example texts:
- “what RFIs are open on 12 Oak?”
- “any open RFIs at the Smith job”
Check the schedule
Section titled “Check the schedule”Lists the project’s schedule tasks for today, tomorrow, this week, next week or the next two weeks, with dates and percent complete.
- Asks before doing it? No. It only looks things up.
- Can be undone? Nothing to undo: it doesn’t change anything.
- Procore API call:
GET /rest/v1.0/projects/{project_id}/schedule/calendar_items - Action name:
procore.list_schedule
Example texts:
- “what’s on the schedule at 12 Oak this week?”
- “what’s happening at the Smith job tomorrow”
This list is generated from the code that runs each action, so it’s always current.