Constant Contact's "automation" is a marketing term. It's not automation in the architectural sense. It's basic, static branching logic.
Real automation is event-driven, stateful, and can integrate external data. Constant Contact gives you:
* If subscriber does X, send email Y after Z days.
* Static paths. No real-time decisions.
* No meaningful computation or external API calls mid-flow.
Compare a real workflow engine (like a simple AWS Step Functions state machine) to their "automation":
```json
{
"Comment": "Dynamic lead scoring workflow",
"StartAt": "FetchCRMData",
"States": {
"FetchCRMData": {
"Type": "Task",
"Resource": "arn:aws:lambda:function:fetchData",
"Next": "CalculateScore"
},
"CalculateScore": {
"Type": "Task",
"Resource": "arn:aws:lambda:function:scoreLead",
"Next": "BranchOnScore"
},
"BranchOnScore": {
"Type": "Choice",
"Choices": [
{
"Variable": "$.score",
"NumericGreaterThan": 80,
"Next": "SendToSales"
},
{
"Variable": "$.score",
"NumericBetween": [50, 80],
"Next": "NurtureCampaign"
}
],
"Default": "SendGenericFollowup"
}
}
}
```
Their system can't do this. It's just a pre-defined flowchart. Calling it "automation" is a stretch. It's rules. Simple, rigid rules.
Simplicity is the ultimate sophistication
Oh please. Tell me you haven't been burned by "real automation" falling over because someone's external API call timed out and the whole state machine wedged itself.
Your AWS Step Functions example is exactly the kind of over-engineered solution a marketing team would drown in. They don't need dynamic lead scoring, they need to reliably send a follow-up email three days after a webinar. Constant Contact's "basic rules" handle that without someone having to debug a Lambda's IAM role at 2 AM.
It's automation if it removes a manual step. Not everything needs to be a Turing-complete decision engine. Sometimes static branching logic that actually works is the better architectural choice.
Yeah, it's not a Turing-complete decision engine. But for a lot of the small business folks using Constant Contact, that's the point. They don't need to integrate external APIs mid-flow for a welcome series or a post-purchase follow-up.
"Real automation" in the architectural sense requires a whole other level of maintenance and expertise. If all you need is a reliable, scheduled email based on a simple trigger, their basic rules do technically automate a manual task. It's just automation with very narrow guardrails, which is perfect for some use cases and frustrating for others.
Always testing.