[H]Hashentic
🇬🇧EN🇪🇸ES🇩🇪DE🇨🇳ZH🇷🇺RU🇵🇱PL
Request Demo
// EXAMPLES

Turn product events into useful actions.

Connect scans, form submissions and external events to your team’s next step. These recipes show what you can configure in Hashentic.

// 01 / 03

A product scan that opens the right campaign

A sneaker becomes a campaign touchpoint. Check the scan country, show a launch-interest form to the matching audience and send submitted fields to your system.

Configuration

Configure a country condition and a ShowForm step with consent text. Define the outbound HTTP destination and field mapping. Country data is used when available.

Result

Your system receives a product-linked response after submission. Non-matching scans continue without this campaign form.

Animated preview
01 / TriggerProduct scan
Connected sneaker[H]NFC
NFC / QR
02 / ConditionChoose the audience
Scan countryIT
Condition matched
Otherwise: continue the product page
[H]
03 / ActionShow the campaign form
[email protected]
Agreed to be contacted
Wait for the customer's submissionResponse received
04 / ActionPass on the response
Send the submitted fields to your system
  1. Product scan. A customer opens the product page through NFC or QR.
  2. Choose the audience. Check the country in the scan context against the configured market.
  3. Show the campaign form. Collect an optional expression of interest and the configured consent.
  4. Pass on the response. Send the mapped fields to your system through an HTTP request after submission.
Illustrative configuration. The matched branch waits for form submission; HTTP delivery runs only afterward. Nothing is submitted here.
// 02 / 03

Suspicious scan review

Route a detected risk to the right people using a condition and a notification.

Configuration

Enable fraud detection and workflows. Set the condition and choose the team’s notification destination.

Result

A reviewer can acknowledge, dismiss or confirm the case. Blocking is a separate configured action.

Animated preview
01 / TriggerRisk detected
Scan count0311
02 / ConditionCheck a condition
Scan count> 10
Not matchedEnd this workflow branch
Condition matched
03 / ActionAdd notification

A signal to investigate, linked to this product.

04 / ActionSend email
[email protected]

The team reviews the alert. Blocking requires a separate configured action.

  1. Risk detected. A configured fraud signal triggers the flow.
  2. Check a condition. Match the risk context you care about.
  3. Add notification. Create a notification for the team.
  4. Send email. Alert the responsible reviewer.
Example configuration. Conditions, recipients and integrations are set by your team.
// 03 / 03

External system update

Accept an authenticated webhook and update the associated product record.

Configuration

Configure the webhook secret, target product and field mapping. Test against a sample payload.

Result

The product data and label reflect the received event; the team gets a notification.

Animated preview
01 / TriggerReceive webhook
ERP → HASHENTIC
{
event: shipment.dispatched,
productId: 2048,
status: shipped,
batch: LOT-024
}
Authenticated event
02 / ActionUpdate fields
status → status
batch → batch
Product record#2048
Status
PreparingShipped
BatchLOT-024
03 / ActionAdd a label
Shipped
04 / ActionNotify the team
Product fields and label updated; team notified.
  1. Receive webhook. An external system sends an event.
  2. Update fields. Map the payload to custom fields.
  3. Add a label. Identify the new product status.
  4. Notify the team. Surface the completed update.
Example configuration. Conditions, recipients and integrations are set by your team.
Discuss this scenarioExplore forms