Workflows
Automate repetitive work with triggers, conditions and actions — periodic and date-based triggers, workflows that start each other, a canvas editor, suggestions from your data, branching, waiting, HTTP and AI steps.
Workflows (sidebar → Workflows, admins) run actions on records in order when something happens — an opportunity is created, a stage changes, an email arrives from a company… — or at a set time. The editor is a canvas: Trigger → Conditions → Steps are blocks linked by arrows; branches open side by side, and a workflow can start another workflow (Chain). (Labels are shown in Turkish in the app.)
Triggers
| Trigger | Object | When |
|---|---|---|
| Opportunity created · Opportunity stage changed | Opportunity | Right after saving |
| Opportunity idle for N days · Stage time (SLA) exceeded | Opportunity | Daily check |
| Company created · Company visit overdue | Company | Immediately · daily |
| Fair lead entered · Visit / call logged · Support ticket opened | The record | Immediately |
| Contract end approaching | Contract | Daily |
| Email received from a company | During sync | |
| Order entered | Order | Immediately |
| Invoice due date approaching / passed | Invoice (ERP) | Daily — N days before, on the due date or N days after |
| Order scheduled for delivery · carried over to the next run · shipped · delivered | Order | Immediately (Shipping) |
| Before the delivery day | Order | Daily — N days before the run |
| Run manually — opportunity / company | Opportunity · Company | When a user starts it |
| Scheduled — opportunities / companies | Opportunity · Company | Every day / week / month at a chosen hour |
| Periodic — for every company | Company | Every N months / weeks / days from a start date (Periodic) |
| A company date field approaches | Company | N days before / after a date field, optionally every year |
| Time to reorder | Company | Based on the company's own order frequency |
| N days after an order | Company | Once per order — optionally by product and repeating at an interval (maintenance) |
| Periodic — during a contract | Contract | Every N months from the start of a signed contract, stops at the end |
| A quote is about to expire | Opportunity | A quote on an open opportunity expires within N days |
| Started by another workflow — company · opportunity · contract · ticket · visit | The record | Only through the Start workflow step (Chain) |
Manual workflows run from the Workflow button on opportunity and company pages, or from the Workflow menu in the bottom bar for selected records in a table view (edit rights on the record are required).
A scheduled workflow runs once per period, for every record matching its conditions (at most 500 records per run). Example: Every Monday 09:00 — add an AI summary note to open opportunities.
Periodic and date-based triggers
These triggers are evaluated once a day and run once per company (or contract, order, quote) per period. Evaluate now on the workflow page runs them right away.
| Trigger | Settings | Example |
|---|---|---|
| Periodic — for every company | Every N months / weeks / days, start date (last call · last face-to-face visit · last order · first order · date the company was added · a company date custom field), per-company interval (number custom field, e.g. Maintenance interval (months)), start N days early, fall back to the date added | A call every 6 months: a task for every active customer not called for 6 months — logging a call resets the counter |
| A company date field approaches | date custom field, N days before / after, every year | Service contract 60 days before warranty end; check-up on the installation anniversary |
| Time to reorder | product group, minimum orders (3+), percentage of the interval (90%) | A call when 90% of the company's median order interval has passed |
| N days after an order | days, product group, product, then every N days · how many times in total | Delivery and satisfaction call 10 days after the order · Periodic maintenance of sold products: 180 days after the sale, then every 180 days, 4 times |
| Periodic — during a contract | every N months, N days early | Contract service visit every 3 months |
| A quote is about to expire | days left | Decision call 7 days before expiry |
- Due date = start date + interval. On the first evaluation it runs once for every overdue record; after that only for new periods.
- Reorder timing comes from the company's own history: cancelled orders don't count and at least two intervals are needed.
- The quote trigger only looks at presented or approved quotes on open opportunities; quotes already turned into orders are skipped.
- With a repeat on the after-order trigger, each order line is tracked separately (two products sold to a company on two dates get separate maintenance tasks); texts can use
{ürün}(product),{miktar}(quantity) and{bakım}(service number). Industry package - Texts can also use
{vade}(due date),{dönem}(period number),{aralık}(interval or median order interval) and{gün}(days elapsed or left).
Conditions
A condition is field + operator (=, ≠, contains, ≥, ≤, empty, not empty) + value. With two or more conditions choose Match: All (AND) or Any (OR) — e.g. amount ≥ 100,000 OR payment term ≥ 60 days. Branch and goal conditions have the same choice. Opportunity and company custom fields can be used too. Without conditions the workflow runs for every triggering record.
Company, opportunity, visit, ticket and contract workflows can also use company metrics: days since the last call, days since the last order, orders in the last 12 months, product groups bought in the last 12 months, open opportunities, overdue balance and the oldest overdue invoice in days (from the ERP connection). Example: product groups in 12 months = 1 → cross-sell task.
Opportunities also offer idle days, days in stage, days to close, payment term, loss reason and quote status; leads whether email / phone are filled, status and first touch; companies district, shipping region and credit hold; orders days to due date, carry-overs and PO; invoices remaining amount and days overdue.
Steps
| Step | What it does |
|---|---|
| Create task | Title, due in N days, assignee, type, priority |
| Write email | Your own subject and body (no template needed); to the record's contact, the email's sender, the owner, the owner's manager or a fixed address. Draft or send directly (Send mode) |
| WhatsApp message | Free text or a Meta-approved template to the contact (with WhatsApp Business connected); otherwise a task for the owner with a wa.me link |
| Add calendar event | Title, in N days, time, duration, on-site / online, location; for whom |
| Open opportunity | Name, stage, type, amount (empty · copy the record's amount · fixed) — for renewals and win-back; not opened twice while one with the same name is open |
| Request approval | The workflow stops here; continues when approved, stops when rejected (Approval) |
| Send notification | To the record owner, the workflow's creator, a chosen user, or all admins |
| Assign owner · Add tag · Update field | Changes the record (custom fields included) |
| Send email (template) · Send SMS · Add to email sequence | Email / SMS / sequence to the contact (sequences need the Email Automation module); email and SMS have a send mode |
| Send to app | Slack, Teams, Telegram, webhook… (Apps) |
| Branch on condition | Runs the If yes steps when conditions hold, otherwise the If no steps |
| Wait | Continues the remaining steps after N days / hours |
| Send HTTP request | Calls your own system (ERP, automation without Zapier) |
| AI step | Classifies, summarizes or writes to an instruction; writes the result to a custom field or as a note on the record |
| Start workflow | Starts the chosen workflow on the same record or the record's company (Chain) |
Writing {bugün} in an Update field step on a date custom field stores the day it runs (e.g. Last maintenance date).
Variables, formats and fallbacks
Add variable under a text field (or Variables at the bottom of the editor) opens a searchable, grouped list — contact, company, owner and manager, opportunity, quote, order and delivery, invoice, contract, lead and fair, dates and links — each with an example. Clicking inserts it at the cursor. The main ones: {kişi_ad} (contact first name) {kişi} {kişi_unvan} {firma} {firma_il} {sorumlu} {sorumlu_tel} {yönetici} {ben} {fırsat} {aşama} {tutar} {ödeme_vadesi} {teklif_no} {teklif_tutar} {sipariş_no} {po} {termin} {sevk_tarihi} {takip_link} {fatura_no} {kalan} {gecikme} {sözleşme_bitiş} {fuar} {kayıt_link} {bugün} — the older variables ({gün} {vade} {dönem} {aralık} {ürün} {miktar} {bakım} …) still work.
- Fallback:
{kişi_ad|Yetkili}— writes Yetkili when the contact name is empty. - Money and numbers:
{tutar:kuruşlu}→ 150.000,00 ₺ ·{tutar:para}→ 150.000 ₺ ·{miktar:sayı}→ 1.250 - Dates:
{vade:uzun}→ 28 Ekim 2026 ·{vade:kısa}→ 28.10 ·{vade:gün}→ Çarşamba - Case:
{firma:büyük}→ UPPER CASE ·{firma:baş}→ Title Case ·{kişi:ilk}→ first word - Format and fallback together:
{sevk_tarihi:uzun|yeni tarih}
An unknown variable stays in the text as written. Meaning by industry shows what the same variable stands for in manufacturing / wholesale, software, field service and consulting. Preview with a sample record fills the text from one of your recent records and lists empty variables so you can add a fallback.
Send mode
Chosen per step for email, SMS and WhatsApp going to customers: Draft — owner approves (default; the email lands in Emails › Outbox as workflow · awaiting approval and the owner is notified; SMS and WhatsApp drafts become a task for the owner) or Send directly (within business hours if set). Email-template and SMS steps created before v96 keep sending directly.
Request approval
Who approves (the owner's manager, any admin or a specific person), a title and the text the approver sees (with variables: {firma} — {tutar} / {ödeme_vadesi} days), a duration (days) and on expiry stop or continue. The workflow waits; the approver is notified and requests are listed under Workflows › Approvals. Approved: the remaining steps run immediately; rejected: the workflow stops and the owner is told. The record owner can't approve their own request. Approval can't be used inside a branch.
Sending rules: business hours and goal
The Sending rules block after the conditions on the canvas holds two settings:
- Business hours (e.g. weekdays 09:15–18:00): a direct email, SMS or WhatsApp to a customer due outside hours waits until the next opening (outside hours — step 2 queued for 26.10 09:15). Drafts and internal notifications don't wait.
- Goal / exit criteria: once the goal is reached, the remaining steps don't run — the contact replied, a visit / call was logged, the opportunity stage changed, the opportunity was won, a quote was sent, an order was entered, the invoice was paid, the order was shipped, or conditions you define hold. Checked after every wait and queue; Runs shows goal reached (…) — stopped.
Branch on condition
A branch has its own conditions (independent of the workflow's conditions). Add as many steps as you like to each arm; branches and waits can't be nested inside an arm. An empty arm means "do nothing".
Wait
At a Wait step the workflow pauses and queues the remaining steps; when the time is up (via the 10-minute scheduler) it continues from where it stopped. With Re-check conditions when the time is up, the workflow's conditions are checked again before continuing — if they no longer hold (e.g. the opportunity moved on in the meantime), the workflow stops. Wait can't be the last step. If the workflow is disabled or deleted, queued steps don't run.
Template Post-presentation follow-up (wait + branch): when an opportunity moves to Present Solution, create a task → wait 5 days → if it's still in the same stage, notify the owner and the admins.
Send HTTP request
Method (POST, PUT, PATCH, GET, DELETE), URL (https:// and public addresses only; variables allowed), optional headers (one Name: value per line) and body.
With Send record data as JSON checked the body looks like this (text in the body field is added as message):
{
"event": "workflow",
"workflow": "Send to ERP",
"workflow_id": 7,
"kind": "opp",
"id": 412,
"url": "https://acme.solk.app/opportunities/412",
"data": {"owner": "3", "c_status": "AC", "c_city": "İzmir", "stage": "Win", "value": 324000.0, "prob": 100, "tag": "", "...": "..."},
"vars": {"firma": "Egemen Group A.Ş.", "fırsat": "Proje · 2026", "...": "..."},
"sent_at": "2026-10-04T14:20:05",
"message": "Proje · 2026 won"
}data holds the field values used by conditions (owner = user id, c_* = the company's fields, custom fields as cf_<key>).
Unchecked, the body is sent as written (with variables filled in) — Content-Type: application/json if it's valid JSON, plain text otherwise. With a signing secret the request carries X-Solk-Signature: sha256=<HMAC-SHA256(secret, body)> — verified the same way as webhooks. A non-2xx response fails the step; the result shows in the Runs tab. Requests time out after 15 seconds.
AI step
| Operation | Result |
|---|---|
| Classify | Picks one of the options you give (or the options of the target select field) |
| Summarize | Summarizes the record's current state in a few sentences |
| Write to instruction | Answers your instruction using the record's information ("Suggest the next step in one sentence") |
The result is written to a text / long text / select custom field of the opportunity or company, or as a note on the record. The AI receives a summary of the record: stage, amount, owner, custom fields, stage history, company details, contacts' names and titles, recent calls, notes and recent email subjects. Contacts' email addresses and phone numbers are never sent. If AI is off for the organization the step fails and nothing is sent; every run counts toward AI usage.
Chain: Start workflow
The Start workflow step starts the chosen workflow right away, so stages link up: maintenance visit logged → last maintenance date becomes today → the spare-parts quote process starts.
- The target runs on the same record type, or it is a company workflow (then it runs on the record's company). The target's own conditions are checked.
- For a workflow that should only run in a chain, pick Started by another workflow as its trigger; the editor shows which workflows start it.
- If the target is off the step fails. Loops (A → B → A) and chains longer than 6 workflows are stopped while running; the result shows in Runs as → target: started or as an error.
- Workflows → Links shows chains in columns with arrows, with warnings for disabled workflows and loops. In the list a chain badge marks chained workflows. Deleting a workflow that a chain starts shows a warning.
Canvas and list view
The editor opens on a canvas: the trigger, the conditions and every step are blocks linked by arrows, flowing row by row. Each block carries a status chip — Ready, or what is missing such as Missing: sequence.
- Click a block to open its settings in the side panel (bottom sheet on phones); move a step earlier / later or delete it from the panel.
- + on an arrow inserts a step there; Add step at the end appends one.
- A Branch on condition block connects its Yes and No outputs to two columns below, each with its own + Step button. After the branch the next step continues.
- Below the canvas you see recent runs and the 30-day count.
- List view is the earlier sequential editor; your choice is remembered in the browser.
Templates and suggestions from your data
The New workflow page has three parts:
- Suggestions from your data: computed from your records and backed by numbers — e.g. no call logged with 38 active customers in 6 months, 12 customers are due to reorder, 4 quotes expire within 14 days, overdue balance at 7 companies. Each suggestion lists example companies and installs with one click (Install); installed ones show Installed.
- Linked processes: workflows installed together that start each other — Maintenance cycle (maintenance due → appointment; maintenance visit → date renewed → spare-parts quote), New customer: from win to day 90, Quote → decision → after a loss.
- Templates: filter by category (Maintenance and spare parts · Regular customer relationship · Sales and quotes · Collections and orders · Shipping and delivery · General). Advanced templates come first in their category; the features they use (OR conditions, business hours, goal, approval, draft approval, calendar…) appear as chips on the card. Each template explains why it works, what to measure and what installing adds.
Installing creates what a template needs: company custom fields (Last maintenance date, Maintenance interval (months), Warranty end, Machine installation date), a draft email sequence and the workflow it starts in a chain. The spare-parts product group is picked from your product list and the quote stage from your pipeline. Everything is installed off; review it on the canvas and switch it on.
Advanced templates (v96): Hot contact after a fair (hot OR warm lead; draft email, WhatsApp, task; stops on a reply or a visit) · Cooling lead: the 48-hour rule (no contact in 2 days → owner and their manager) · Opportunity stuck in the quote stage (5 days idle → draft reminder to the customer and a follow-up task; stops when the stage changes) · High amount or long payment term: manager approval · Time to reorder: personal reminder · Periodic maintenance: appointment email to the customer (+ calendar) · Gentle reminder before the due date (3 days before) · Overdue: staged collection (days 1, 7 and 14; stops when paid) · Contract renewal: open an opportunity + tell the customer (30 days before, amount copied) · Win back a lost opportunity (loss reason Budget / Timing) · Won opportunity: notify the ERP + kickoff meeting · and the four Shipping and delivery templates. All install off; steps to customers default to draft.
The email sequence gallery filters by the same categories; 12 new sequences (maintenance reminder, spare-parts renewal, warranty, reorder, after the order, gentle payment reminder, welcome, win-back, price update, quarterly review invite, after a loss, quote expiry) come with their rationale.
Runs and limits
- The Runs tab shows each run with record, result and a step summary (HTTP POST erp.example.com → 200 · branch: no · tag 'Small deal' · waiting → 06.10.2026 · approval requested → Selin Aras (2 days)).
- Changes made by a workflow don't trigger other workflows; use the Start workflow step for deliberate links (loops and chains longer than 6 are blocked).
- Periodic and date-based triggers look at up to 3,000 records per workflow per evaluation.
- More than 200 events in one request (such as a bulk import) don't run workflows.
- Workflows don't run on sample-data records.