Harvest + Targetprocess Integrations

How to connect Harvest + Targetprocess

Zapier lets you send info between Harvest and Targetprocess automatically—no code required.

When this happens...

automatically do this!

Popular Harvest + Targetprocess workflows

Our most popular Zap! arrow pointing down

Create new tasks on Harvest for new bugs on TargetProcess
Try it
Targetprocess + Harvest
More details
When this happens
Step 1: New Bug
Then do this
Step 2: Create Task
See Zap details Try it
Create new tasks on Harvest for new bugs on TargetProcess
Create new tasks on Harvest for new bugs on TargetProcess
Targetprocess + Harvest
Create Harvest tasks for new TargetProcess tasks
Try it
Targetprocess + Harvest
More details
When this happens
Step 1: New Task
Then do this
Step 2: Create Task
See Zap details Try it
Create Harvest tasks for new TargetProcess tasks
Create Harvest tasks for new TargetProcess tasks
Targetprocess + Harvest

Connect your apps and automate workflows

Easy automation for busy people. Zapier moves info between your web apps automatically, so you can focus on your most important work.

By signing up, you agree to Zapier’s Terms of Service and Privacy Policy

Supported triggers and actions

What does this mean?

New User Assignment
Triggers when a person is assigned to a project.
Trigger
Scheduled
New Client
Triggers when you add a new client.
Trigger
Scheduled
New Contact
Triggers when you add a new contact.
Trigger
Scheduled
New Invoice
Triggers when you add a new invoice.
Trigger
Scheduled
New Invoice
Triggers when you add a new invoice (with line item support).
Trigger
Scheduled
New Person
Triggers when you add a new person.
Trigger
Scheduled
New Project
Triggers when you add a new project.
Trigger
Scheduled
New Task
Triggers when you add a new task.
Trigger
Scheduled
Harvest
Triggers when a new timesheet entry is created for today.
Scheduled
Trigger
Harvest
Adds a new client.
Scheduled
Action
Harvest
Adds a new contact.
Scheduled
Action
Harvest
Creates a project.
Scheduled
Action
Harvest
Creates and starts a timer for the current day.
Scheduled
Action
Harvest
Stops the timer for the current day (if one is running).
Scheduled
Action
Harvest
Adds a new task.
Scheduled
Action
Harvest
Creates a new timesheet entry for the current day.
Scheduled
Action
Targetprocess
Triggers when a new Bug is added.
Scheduled
Trigger
Targetprocess
Triggers when a new Build is added by user.
Scheduled
Trigger
Targetprocess
Triggers when a new Comment is added to some Entity.
Scheduled
Trigger
Targetprocess
Triggers when new Feature is added by user.
Scheduled
Trigger
Targetprocess
Triggers when a new Iteration is added.
Scheduled
Trigger
Targetprocess
Triggers when a new Release is added.
Scheduled
Trigger
Targetprocess
Triggers when a new Request is added.
Scheduled
Trigger
Targetprocess
Triggers when a new Task is added by user.
Scheduled
Trigger
Targetprocess
Triggers when a new Team Iteration is added.
Scheduled
Trigger
Targetprocess
Triggers when a new Time record is added to some Entity by User.
Scheduled
Trigger
Targetprocess
Triggers when a new User Story is added.
Scheduled
Trigger
Targetprocess
Create new User-Requester and attach her to existing Request.
Scheduled
Action
Targetprocess
Change state of existing Entity. .
Scheduled
Action
Targetprocess
Creates a new Bug (defect, error, flaw, mistake, failure or fault in a computer program). Can relate to User Story. Can be assigned to Release and Iteration.
Scheduled
Action
Targetprocess
Creates a Build entity in a project. Bugs and source code Revisions can be assigned to Build.
Scheduled
Action
Targetprocess
Appends a new Comment to existing Entity.
Scheduled
Action
Targetprocess
Create a Feature, a high-level requirement which contains User Stories.
Scheduled
Action
Targetprocess
Creates a Request, which can represent idea, issue or question from users.
Scheduled
Action
Targetprocess
Creates a Task, a small chunk of work, typically less than 16 hours. Task must relate to User Story.
Scheduled
Action
Targetprocess
Create a Time record by User for specific Entity.
Scheduled
Action
Targetprocess
Creates a User Story, a statement of end user requirements in a couple of sentences. User Story can be assigned to Iteration or Release.
Scheduled
Action
Targetprocess
Deletes an Entity, which follows selected criteria.
Scheduled
Action

How Harvest + Targetprocess Integrations Work

Step 1: Authenticate Harvest and Targetprocess.
30 seconds
Step 2: Pick one of the apps as a trigger, which will kick off your automation.
15 seconds
Step 3: Choose a resulting action from the other app.
15 seconds
Step 4: Select the data you want to send from one app to the other.
2 minutes
That’s it! More time to work on other things.