03Sales and support · Salesexample setup · demo data

A form submission lands in the CRM with its score and the reasons.

An example setup for a sales team that wants to sort website leads quickly: a lead doesn’t wait, it lands in the CRM with its score and the reasons.

It runs on your own server: work files and records are stored on your infrastructure; content processed by AI goes to the model provider you choose, and data sent to external tools goes to the connections you set up.

demo data
01Workflowfrom the chat or the editor

Lead intake

It starts from a ready template: a signed webhook brings in the lead, company data is fetched and a JavaScript step scores it by your rules. The threshold and the branches are entirely yours.

demo data

Last run · 11:42 · score 82 · hot

02Setup and flowSales

Setup and flow

A sales team that wants to sort leads from the website quickly.

Setup

Start
The ready “Lead intake” workflow template, triggered by a signed webhook. A project admin or the owner sets up the webhook automation.
Connections
The API keys of a company-data service and of your CRM in the vault, bound to their addresses.

What a day looks like

  1. 01

    The form is submitted; the signed request starts the workflow.

  2. 02

    Company data is fetched (the lead is not lost if the service doesn’t answer); a JavaScript step computes a 0–100 score and the reasons.

  3. 03

    Leads above the threshold are written to the CRM as “hot” and the team gets a notification; the rest go to the “nurture” list.

What changes

A hot lead is in front of the team within minutes, and why it stood out is on the record.

How it connects

Your form or form service starts the workflow with a signed webhook; if it doesn’t produce the signature, you put a small signing step in between (n8n, Zapier, Make or your own function). You reach your CRM and the company-data service with the HTTP step and set the fields to fit your own setup.

We don’t impose a ready-made flow; design your own, either with AI (describe it in the chat) or yourself (in the workflow editor).

Good to know

  • The scoring is a code step that runs your rules; if you like, you add an AI step that drafts a personal welcome email, plus an approval.
  • In flows with personal data, you set the privacy notice and retention period to match your data protection policy (KVKK or your local law); workflow data retention is set in the panel.
demo dataAudit log: every privileged action, with chain verification and export.
A screen from the console · The real console: the audit log, who set up and changed what.
03Other use cases

Another team’s recurring work

All use cases and the connection process

Let’s fit this setup to your own work.

This example runs on the same infrastructure as all the others: Remyral on your own server, and we build your flow together in the pilot. Just describe the work you want to simplify and the tools you use in your application.