Wojtek Woźniak — no-code ops at tonik
Crafting no-code elixirs: from email flows to kick-ass apps.
September 5, 2023
10:00
No-Code
🇵🇱 Polish
No-Code
Tools and automations that allow me to work 10x more efficiently
About
See a number of tools that help me in my daily work, significantly increasing my efficiency. In addition to no-code tools, I'll show you their practical applications and the optimizations I create using robots. We'll look at how you can improve your workflow with the help of make.com scenarios and you'll also see how Alice - my personal AI assistant - works.
Talk by
Grzegorz Róg
CEO at easy_
Watch the full talk
Watch this WaysConf session, then continue with related talks or explore the current programme.
From the recording
Talk in brief
A practical tour of no-code tools and automations that remove repetitive operational work from a product creator’s day. The talk demonstrates how services such as Make, Airtable, Notion, mobile shortcuts, webhooks, and AI-assisted formatting can move information between systems, create internal interfaces, publish content, and document workflows. The useful principle is not to automate everything: start with a recurring process, define the data entering and leaving it, connect proven tools, and keep enough visibility to diagnose failures.
Key takeaways
- 01
Model automation as inputs and outputs
A workflow becomes easier to design when teams first name the triggering data, the transformations it needs, and the destination that should receive it.
Watch from 2:36 - 02
Automate routine work to protect creativity
Email, scheduling, and repetitive coordination are strong candidates for automation because removing them creates more time for valuable creative decisions.
Watch from 8:53 - 03
Prototype operational systems without code
Webhooks, databases, and configurable interfaces can validate an internal process before a team commits engineering time to custom software.
Watch from 22:14 - 04
Reuse structured content across channels
A single source in Notion or another database can feed newsletters, announcements, images, and social formats through predictable transformations.
Watch from 29:22 - 05
Generate documentation from workflow definitions
Exported automation blueprints can help explain complex scenarios and expose possible failure points when reviewed with an appropriate analysis tool.
Watch from 45:00
Read edited transcript highlights
These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.
Begin with the movement of information
A useful automation can be described before any tool is selected. Identify what event starts it, which information arrives, how that information must change, and where the result belongs. Visual automation platforms make these steps visible, allowing a creator to test the logic quickly and replace individual services without redesigning the entire process.
Watch from 2:36Productivity should return attention to meaningful work
The value of a faster email client or a connected workflow is not the number of actions it performs. The benefit is reduced context switching and less time spent repeating predictable coordination. Automation is most worthwhile when it protects the concentration needed for design, writing, customer conversations, and other work that still depends on judgment.
Watch from 8:53No-code prototypes can validate operations
A checkout can send structured information through a webhook, a database can store it, and a configurable interface can reveal sales trends. This combination creates a working operational system quickly enough to learn from real use. If the process proves valuable, the evidence then supports a better-informed decision about custom engineering.
Watch from 22:14One content source can support many formats
Publishing becomes less repetitive when the original content is structured consistently. An automation can retrieve a newsletter draft, create supporting assets, prepare announcements, and adapt the wording for several destinations. Human review remains important, but the mechanical preparation no longer has to be repeated separately for every channel.
Watch from 29:22Maintainability matters after the demonstration
Visual scenarios can become difficult to understand as they grow. Exporting the workflow definition creates a record that can be analyzed, documented, and discussed. Teams should use that record to name dependencies, likely failure points, and recovery steps so a useful automation does not become an invisible production risk.
Watch from 45:00
Explore WaysConf 2026
