Integration with external services via Zapier connector

Zapier is a third-party service that allows Targetprocess to connect to many tools. It acts as a mediator between the tools communicating via API. This provides new possibilities for automating the routine or getting your systems synchronized.

Here is a short list of cool integrations and features that are possible with Zapier:

• Zendesk -> Targetprocess: every time a new ticket is created in Zendesk, a new request is added in Targetprocess.
• Github Issues-> Targetprocess: a bug or request is created when a new github issue is added.
• Targetprocess -> Gmail or SMTP: send an email for specific actions and conditions (yes, it’s your custom way to manage email notifications).
• Google Doc -> Targetprocess: a user story created when a new row is added to the spreadsheet (an alternative way to import and export, by the way).
• Twitter -> Targetprocess: a request is created for the tweets to your support account
• Disqus -> Targetprocess: never miss a new comment posted to your website or blog (we use it for our guides).

That’s just off the top of the head, and we are sure you’ll come up with many more ideas to enhance your Targetprocess experience. There are hundreds of tools for you to choose from, you are welcome to explore and experiment. And if you have your own tool and would like to integrate it with Targetprocess, you are also welcome to post your API to Zapier so that we can connect our tools easily.

Before we dig into the details, there is a couple of things we have to note:

• The integration works as a “trigger” only for new events, it won’t import existing items from the systems you are connecting.
• Zapier uses a separate pricing model based on the count of transactions. There is a free plan, but it has limitations.

How it works

In a nutshell, the integration is based on two main elements: trigger (when this happens) and action (then do this):

So, what can Targetprocess do via Zapier?

Supported Triggers

• New Comment - Triggers when a new Comment is added to some Entity.
• New Task - Triggers when a new Task is added by the user.
• New Request - Triggers when a new Request is added.
• New Bug - Triggers when a new Bug is added.
• New Feature - Triggers when new Feature is added by the user.
• New User Story - Triggers when a new User Story is added.
• New Iteration - Triggers when a new Iteration is added.
• New Team Iteration - Triggers when a new Team Iteration is added.
• New Release - Triggers when a new Release is added.
• New Time - Triggers when a new Time record is added to some Entity by User.

Supported Actions

• Create Task - Creates a Task, a small chunk of work, which typically requires less than 16 hours of work. The Task should belong to some User Story.
• Create User Story - Creates a User Story, a statement of the end-user requirements worded in a couple of sentences. The User Story can be assigned to an Iteration or Release.
• Create Comment - Adds a new Comment to the existing Entity.
• Add Requester To Request - Create a new User-Requester and attach her to the existing Request.
• Create Feature - Create a Feature, a high-level requirement which contains User Stories.
• Delete Entity - Deletes an Entity, which meets the selected criteria.
• Create Request - Creates a Request, which can be an idea, issue or question from users.
• Create Bug - Creates a new Bug (defect, error, flaw, mistake, failure or fault in a computer program). It can belong to a User Story. Can be assigned to a Release and Iteration.
• Change State - Changes the state of the existing Entity.
• Create Time - Create a Time record by User for specific Entity.

Creating a zap with Targetprocess

Let’s create a new integration (zap) between Github and Targetprocess, so that Github Issues trigger new requests in Targetprocess. After selecting the trigger and action, you'll need to connect your Targetprocess account to Zapier.

You can use an existing account, or create a new connection. In the latter case, you’ll see this screen:

For example:

Copy the token value without quotes, paste it into the authentication field and click “Continue”

Zapier will automatically test if your authentication token is good, and you'll be allowed to continue setting up your Zap.

Now you need to configure the trigger. The fields depend on the application you use, but usually it is something intuitive:

You can also set up filters here if needed.

After that you’ll need to match the trigger and the action. Here you decide which of the trigger’s fields you need and what properties of the action they will affect. Certainly, the fields here vary depending on the application and action:

In the example we are using, we can also recommend specifying the ID of the project for the new request.

Now please test the zap, name it, turn it on and enjoy!