Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Greip

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.

CategoryDeveloper Tools
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Greip with Flows360

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.

Use the Greip connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 5 triggers.

Available actions

  • ASN Lookup
  • BIN Lookup
  • IP Lookup
  • Email Validation
  • Detect Profanity
  • Phone Validation

Available triggers

  • Proxy Connection Detected
  • Fraudulent Payment Detected
  • Profanity Text Detected
  • Spam Email Detected
  • Spam Phone Number Detected

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Greip
  • Package: @activepieces/piece-greip@0.1.7
  • Exact artifact digest: sha256:8df8cc7b3c2074122c779a10a4229f04f0382f9f4ed6229fa323921da1c62d12
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • ASN Lookup (asn_lookup), Look up details of an Autonomous System Number (ASN) Classification: read.
  • BIN Lookup (bin_lookup), Look up details of a Bank Identification Number (BIN) or Issuer Identification Number (IIN) Classification: read.
  • IP Lookup (ip_lookup), Look up comprehensive information about an IP address including location, ISP, security, and risk factors Classification: read.
  • Email Validation (email_validation), Validate email addresses by checking domain validity, detecting disposable emails, and assessing risk factors Classification: read.
  • Detect Profanity (profanity_detection), Detect offensive or inappropriate language in text using machine learning Classification: read.
  • Phone Validation (phone_validation), Validate phone numbers by checking syntax and assessing validity and operational status Classification: read.

Trigger contracts

  • Proxy Connection Detected, webhook.
  • Fraudulent Payment Detected, webhook.
  • Profanity Text Detected, webhook.
  • Spam Email Detected, webhook.
  • Spam Phone Number Detected, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects11
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
ASN Lookup Yes No Look up details of an Autonomous System Number (ASN)
BIN Lookup Yes No Look up details of a Bank Identification Number (BIN) or Issuer Identification Number (IIN)
IP Lookup Yes No Look up comprehensive information about an IP address including location, ISP, security, and risk factors
Email Validation Yes No Validate email addresses by checking domain validity, detecting disposable emails, and assessing risk factors
Detect Profanity Yes No Detect offensive or inappropriate language in text using machine learning
Phone Validation Yes No Validate phone numbers by checking syntax and assessing validity and operational status
Proxy Connection Detected Yes No webhook trigger declared by the pinned package.
Fraudulent Payment Detected Yes No webhook trigger declared by the pinned package.
Profanity Text Detected Yes No webhook trigger declared by the pinned package.
Spam Email Detected Yes No webhook trigger declared by the pinned package.
Spam Phone Number Detected Yes No webhook trigger declared by the pinned package.

Setup

Setup

  1. Add the Greip connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-greip@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Greip connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-greip@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com