Clear triggers
Record created, record updated, specific field changed, time reached, webhook received — pick from a menu.
No-code automations: trigger → condition → action
14 trigger types, conditions on any fields, action chains, webhooks, and secrets. Up to 10 runs per minute per chain. Without n8n or Zapier.
demo-стенд · Конструктор автоматизаций
Демо-стенд скоро поднимется.Здесь будет настоящая публичная ссылка на «Конструктор автоматизаций» из продукта.
Problem
Every routine step is a missed deal
A manager forgot to notify the copywriter, an engineer forgot to update the status, the PM was missed. Every such mistake costs money. Struktura automations close these gaps with a scenario you configure once.
Features
What's inside the automation engine
Conditions and filters
AND/OR conditions on record fields. Run an automation only for the rows you need, not all of them.
Action chains
Create a record, update, send a notification, call a webhook — in sequence. Intermediate results are available as variables.
Webhooks
Both inbound (POST trigger) and outbound (action). Connect 1C, BI, Slack, Telegram, any systems.
Run history
Each automation run is logged: input, steps, errors. Debug through the UI, without reading server logs.
Secrets manager
External system API keys are stored separately, not exposed in steps. Access is by base role.
Anti-recursion
A 10-runs-per-minute limit on each automation protects against accidental loops where one automation triggers another.
Templates
Pre-built scenarios: 'notify owner', 'create linked task', 'send proposal to client'. Loaded with one click.
How it works
From idea to launch in 10 minutes
- 1
Describe the trigger
What has to happen for the automation to fire: record creation, field change, schedule.
- 2
Add a condition
For example, only if status = 'new' and amount > 100,000 ₽.
- 3
Pick actions
Create a task, post to chat, send a webhook to 1C. Steps run in order.
- 4
Test on a sample record
Run manually, look at the history. Then turn the automation on for everyone.
Scenarios
Two common automation flows
New request → task for the manager
When a record arrives in the 'Client requests' table via a public form, the automation assigns the responsible manager, creates a linked task with a 2-day deadline, and posts to the #sales channel.
- Trigger — record creation
- Condition — segment = 'Enterprise' and budget ≥ 500,000 ₽
- Action 1 — create task, Action 2 — chat message
PM date approaching → ticket for the engineer
A daily schedule checks the equipment table. If preventive maintenance is less than 7 days away — create a ticket for the engineer, send a notification, update the equipment status.
- Trigger — every day at 06:00
- Condition — formula 'pm_date − today ≤ 7'
- Action — create a task and send a webhook to the monitoring system
Comparison
Why Struktura automations beat external ones
| Возможность | Struktura | Notion | Jira | Zapier+Excel |
|---|---|---|---|---|
| Triggers on record fields | ✓ | basic | via add-ons | — |
| AND/OR conditions | ✓ | — | ✓ | — |
| Inbound/outbound webhooks | ✓ | — | via add-ons | — |
| Run history | ✓ | — | via add-ons | — |
| Secrets manager | ✓ | — | via add-ons | — |
| Recursion protection | ✓ | — | — | — |
Take one routine task off your team tomorrow
Launch a simple automation in 10 minutes, try it on a pilot base. The Team plan includes 20 automations.