How I Connected Telegram,Notion and Make to Automate Digital Product Delivery

As a solo founder,I quickly realized that selling a digital product isn't the hard part.

Managing everything after the sale is.

Every order created a series of manual tasks:

.Sending access information
.Updating customer records
.Tracking purchases
.Organizing customer data

None of these tasks were difficult,but they became repetitive very quickly.

So I decided to automate the process.

The Goal

I wanted a workflow that could:

1.Receive customer information automatically
2.Store records in central database
3.Trigger follow-up actions without manual intervention
4.Reduce operational workload

The Stack

I chose the following tools:

.Telegram
.Make
.Notion

Each tool had a specific role.

Telegram

Telegram acts as the communication layer.

It allows users to receive information quickly and provides a simple way to interact with the workflow.

Make

Make is the automation engine.

It connects different services together and handles the logic behind the workflow.

Notion

Notion serves as the operational database.

Customer records,order information,and workflow status are stored in one place.

The Workflow

The basic process looks like this:

Telegram→Make→Notion

When an event is triggered:

1.Make receives the data
2.The data is processed
3.A new record is created inside Notion
4.Follow-up actions can be triggered automatically

The entire process happens without manual data entry.

What Went Wrong

The first version wasn't perfect.

At one point,customer records were being created with incomplete information.

The automation appeared to be working correctly.

No error messages appeared.

After several hours of debugging,I discovered that one field inside a Make module was mapped incorrectly.

It was a small mistake,but it affected the entire workflow.

This taught me an important lesson:

Automation systems don't fail in dramatic ways.

They often fail quietly.

That's why monitoring and testing are just as important as building.

Lessons Learned

After building this workflow,three lessons stood out:

1.Start Simple

It's tempting to automate everything.

Don't.

Building the smallest workflow that solves a real problem.

2.Test Every Connection

Most issues don't come from tools.

They come from assumptions.

Always verify that data is moving correctly between systems.

3.Automation Is About Operations

The technical setup is usually straightforward.

The difficult part is designing a process that makes sense long term.

Final Thoughts

I'm still improving this workflow and experimenting with new approaches.

For now,the biggest benefit isn't saving time.

It's reducing the number of repetitive decisions I need to make everyday.

As a solo founder,that's often more valuable than the automation itself.

Have you built any automation workflows using Telegram,Make,Notion,or similar tools?

I'd love to hear how you're approaching it.