Actions

Note: In order to use any of the Procore actions, you must connect GoFormz to your Procore account. See here for details.

These actions let you manipulate Procore objects. This includes creating, updating and deleting objects, as well as obtaining data from an object. Below, we go over the apiPath input that is required to use these actions, and then list all available Procore actions.

Action scope and apiPath Input

Each Procore workflow action is a wrapper around a set of related Procore API calls that you can find in the Procore developer API documentation. When using Procore actions, it is helpful to have Procore's developer documentation open in a separate tab as a reference.

Each action requires an apiPath input, which is taken directly from the Procore API that is being used. It is the path of the Procore API endpoint, without the vapid prefix. For example, take a look at the Show Company User API in the Procore documentation. It lists GET /vapid/companies/{company_id}/users/{id} as the endpoint. So in order to call this API, you will use /companies/{company_id}/users/{id} as the apiPath input for your action. The {company_id} and {id} in this example are path parameters that must be replaced with the appropriate Procore object IDs.

In practice, the IDs needed for the API call will typically come from other workflow steps. You will reference these using Recipe Workflow Variables. Take a look at this example:

/companies/#{trigger.company_id}/users/#{selectSafetyManager.field_contact_id}

The company ID is taken from the Procore Event trigger, while the user ID is taken from a step called selectSafetyManager in the workflow.

Some Procore APIs also accept query parameters. For instance, take a look at the List Project Roles API. There is a Query Parameters section in the documentation that lists the parameters that you can use. Take a look at this usage example:

/project_roles?project_id=#{trigger.project_id}&role=Safety Manager

The project ID is taken from the Procore Event. This call will return all project role entries within that project that have the role "Savety Manager".

Actions List

  • Create Object: Create a new Procore object and initialize its fields with values. This can be used to perform most "Create" calls in the Procore API.
  • Batch Create Object: Create several Procore objects at once; the objects must be of the same type.
  • Update Object: Send data to an existing Procore object. This can be used to perform most Procore API "Update" calls.
  • Batch Update Object: Update several Procore objects at once; the objects must be of the same type.
  • Upload Attachment: Attach a file to a Procore object.
  • Lookup Object: Extract data from a Procore object. This can be used to perform most Procore API "Show" calls.
  • Query: Get a list of Procore objects. This can be used to perform most Procore API "List" calls.
  • Delete Object: Delete a Procore object. This can be used to perform most Procore API "Delete" calls.

Updated about a year ago

Actions


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.