How to connect PagerDuty + Targetprocess
Zapier lets you send info between PagerDuty and Targetprocess automatically—no code required.
Top companies trust Zapier to automate work and free up time
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.
- New or Updated IncidentTriggers when new incidents are created, or when existing incidents change state.Trigger
- Add Acknowledge EventAcknowledge the incident with this Incident Key.Action
- Add Resolve EventResolve the incident with this Incident Key.Action
- Add Trigger EventTrigger an incident in PagerDuty with this Incident Key.Action
- Find User on CallFind the user on call for a specific schedule.Action
- New BugTriggers when a new Bug is added.Trigger
- New BuildTriggers when a new Build is added by user.Trigger
- New CommentTriggers when a new Comment is added to some Entity.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 PagerDuty + Targetprocess Integrations Work
- Step 1: Authenticate PagerDuty 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.
Related categories
Related categories
Get started for free
You can't add more hours to the day. Zapier is the next best thing.