Skip to content
PagerDuty logoGreip logo

Connect PagerDuty to Greip

Move data between PagerDuty and Greip the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

PagerDuty triggers
3
PagerDuty actions
6
Greip triggers
5
Greip actions
6

Automation ideas

What you can build with PagerDuty and Greip

A few flows teams run between PagerDuty and Greip. Use one as a starting point, or build your own from scratch.

  • New Incident in PagerDuty creates ASN Lookup in Greip

    Triggers when a new incident is created

  • Proxy Connection Detected in Greip creates Create Incident in PagerDuty

    Triggers when a new proxy connection is detected

  • New Incident in PagerDuty creates BIN Lookup in Greip

    Triggers when a new incident is created

  • Proxy Connection Detected in Greip creates List Incidents in PagerDuty

    Triggers when a new proxy connection is detected

  • New Incident in PagerDuty creates IP Lookup in Greip

    Triggers when a new incident is created

  • Proxy Connection Detected in Greip creates Get Incident in PagerDuty

    Triggers when a new proxy connection is detected

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in PagerDuty and acts in Greip, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.