Detect and prevent fraud in your website or app with Greip's Fraud Prevention API. Protect your business from financial losses and gain better insights into your users.
Greip currently provides 5 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
Proxy Connection Detected
Triggers when a new proxy connection is detected
Fraudulent Payment Detected
Triggers when a new fraudulent payment is detected by Greip
Profanity Text Detected
Triggers when Greip detects profanity in a specific text
Spam Email Detected
Triggers when a new email is marked as SPAM by Greip
Spam Phone Number Detected
Triggers when a new phone number is marked as SPAM by Greip
ASN Lookup
Look up details of an Autonomous System Number (ASN)
BIN Lookup
Look up details of a Bank Identification Number (BIN) or Issuer Identification Number (IIN)
IP Lookup
Look up comprehensive information about an IP address including location, ISP, security, and risk factors
Email Validation
Validate email addresses by checking domain validity, detecting disposable emails, and assessing risk factors
Detect Profanity
Detect offensive or inappropriate language in text using machine learning
Phone Validation
Validate phone numbers by checking syntax and assessing validity and operational status
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Greip event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Proxy Connection Detected
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Greip action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
ASN Lookup
Combine Greip with another integration and Coherence records to connect product and engineering activity to the customers and work it affects.
Starts with
Proxy Connection Detected
Finishes with
ASN Lookup, then preserve the outcome in Coherence
The exact authentication fields depend on Greip. The workflow structure stays straightforward:
Authorize the Greip account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Greip or provide a complementary trigger or action.
Greip currently provides 5 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
Greip currently lists 5 triggers and 6 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Greip triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
