My First Automation Didn’t Feel Like a Big Deal
There are some events where we know the first time is a big deal.
We know the first signed of the Declaration of Independence was John Hancock because the Second Continental Congress knew how important it was.
We know Neil Armstrong was the first person to step foot on the moon, which he marked with the eternal words, “One small step for man, one giant leap for mankind.”
There are other times where the events doesn’t seem huge, but is in retrospect.
We don’t really know the text of the first email. It was some keyboard-mashed thing sent by a computer engineer in 1971.
My automation journey seems like the latter (not that me automating is at all similar to any of the events listed here).
When I created my first automation, I didn’t know how transformative automation would be for me.
In fact, when I decided to put an appreciable amount of time into automation back in 2018, it was well after the first time I created an automation.
I had automated parts of my home.
I had auto-responders and automatic bill pay.
I had notifications on my phone.
And, since I’m a programmer, I wrote code that would do stuff for me.
I’ve been automating in way, shape or form for 20 years.
The point being this: automation doesn’t need to be a huge deal when you start (or at all).
It’s about making your life easier…not more complicated.
And it can be a slow burn.
In-fact, this very post is the first step in a new automation I’m testing.
Here’s how it’s going to work:
I want there to be a place on my blog where members (that’s YOU) can read posts without having to log-in to my site.
So my first step is going to be to look for specific information ConvertKit sends when you click on a link.
One of those is your unique subscriber ID.
Eventually, I will store that ID (thanks to Make.com), and you’ll have a completely password-less experience.
But for now, I’m just going to check for the existence of the ID.
One small step.
