Introducing Projects API in public BETA
What is new?
We’re launching three new API resources with a range of endpoints to help you modify the data around the Projects feature space, allowing integrations and automations to join in on providing solutions in the project and task management problem space. The endpoints are tied with the Projects add-on which has to be enabled for the functionality to be used.
Projects API allows to create and manage ongoing, completed or canceled projects attached to an organization, person or to deals. Each project has an owner and must be placed in a phase. Each project consists of standard data fields but can also contain a number of custom fields. The custom fields can be recognized by long hashes as keys.
ProjectsTemplates API allows to have a reusable and dynamic structure to simplify creation of a project. Project templates can contain information about activities, tasks and groups that will be used when creating a project. Currently, only GET functionality is available.
Tasks API allows to create and manage actions that need to be completed inside a project. A task must be associated with a project. Tasks have an optional due date, can be assigned to a user and can have subtasks.
All new endpoints support querying based on cursor pagination. The endpoints are also included in two new OAuth scopes: Projects read and Projects full, see the full division of endpoints in scopes here.
Timeline of the launch
We’re releasing the public BETA today, October 17th, and the API will be available for usage and testing on all accounts. We’ll notify you here in the changelog once the full version of the API is released, so remember to subscribe. Keep in mind that between the BETA and the full release of the API, the endpoints are subject to changes.
Comments
-
Does that mean we will be able to automate stuff with Make/Integromat or Zapier using custom API calls?
0 -
Hi, Will Pipedrive Project be available in Zapier also?
0 -
Hi @Amit Sarda (AmitSarda.xyz) @Torbjörn Johansson
We will reach out to Zapier and Make specifically (as well as to other vendors) to let them know that Projects API is available. However they still need to prioritize the work to support it on their side so I can't give you an ETA on this.
0 -
I meant to ask if we can use the custom API call action in Make to make this work using Make/Integromat?
0 -
For Make.com this is not an issue. If you are technical enough you can do custom Pipedrive API calls. In other words when the endpoints are available you can do this with Make.com
0 -
That IS my question, @J.A.N. (Themakers) - are the endpoints available to use in Make?
0 -
They are accessible already so yes , you can use them with Make. I have tested this.
0 -
Is it possible that there's a typo in the OAuth scope enforcement? I am able to read the project templates with the
projects:readscope, but not with theprojects:fullscope (I get a `Scope and URL mismatch` error). Your scopes documentation also lists `GET /projectTemplates` as a permitted request for the former, but `GET /projectsTemplates` for the latter (which is the wrong route).0 -
0
-
Thanks for adding this API support, and fixing the issues promptly.
We've just added comprehensive integrations with this on relay.app, namely the following:
Automations:
- Create project
- Update project
- Archive project
- Delete project
- Add task to project
- Update project task
Triggers:
- Project created
- Project status changed
- Project phase changed
Waits:
- Project task completed
0 -
one thing that's still missing is to get the projects that are connected to a deal.
I was hoping that calling the "Get A Deal" endpoint would return also a collection of connected projects, but it doesn't 😭
Or give us the option to filter all projects based on a connected deal ID.
0 -
when will we see automation options for projects INSIDE pipedrive??
0 -
Pipedrive Automations already have projects, I believe it was there before the API.
1
