The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
My role. Automation Developer (n8n Workflow Designer)
Project description. Designed and implemented an n8n workflow to automate CSV processing, data transformation, and email campaign execution. The workflow reads and updates CSV files, processes records with custom JavaScript logic, loops through individual entries, controls execution timing, and automates email delivery. This eliminated repetitive manual work and created a scalable workflow for processing large datasets efficiently.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
Automated product publishing saved me 10 mins
I was sick of the manual copy‑paste dance between Google Sheets and WooCommerce for every new drop‑ship item. Using n8n I wired a Telegram command and a schedule trigger to pull the next row, run an IF check, then fire an HTTP POST to WooCommerce. Successful pushes flip the status in Sheets and send a Telegram note; errors land in a separate log sheet. The stack is simple – Telegram Trigger, Schedule Trigger, Google Sheets, IF, HTTP Request – but it shaves about ten minutes per product and gives me a clean audit trail.
#n8n #automation #TelegramTrigger #ScheduleTrigger
Follow for more: https://go.phonezait.de/
InvoiceKit taught me to describe status work as a transition contract, not a dropdown. For each invoice change, I can name the starting state, permitted action, persisted result, and visible confirmation. That structure also gives deterministic UI checks and live Firebase checks distinct jobs. When scoping a workflow, write one acceptance row per important transition. It exposes missing rules earlier and gives the client a reviewable definition of done.
Automation & AI Developers — Ongoing Project Work Across Multiple Clients
#1. What this is
We run an automation agency in Quebec, Canada. We build systems for small and mid-sized businesses that are stuck doing manually what software should be doing for them.
I'm not hiring for one project. I'm building a bench of developers I can bring in as client work comes through the door. Different clients, different industries, different problems — construction, trades, professional services, retail, clinics, logistics. What stays constant is the shape of the work: find the bottleneck, build the system, deploy it, document it, hand it over.
If you're the kind of developer who gets bored building the same funnel twelve times, this is the opposite of that.
---
#2. The kind of work that comes up
You will not do all of this. Tell me which parts are yours.
**Lead capture and response**
- Instant multi-channel response to inbound leads (SMS, email, chat, WhatsApp)
- Voice agents that answer calls, qualify, book, or escalate to a human
- Missed-call text-back, form routing, lead scoring and assignment
**Scheduling and dispatch**
- Booking systems tied to real availability, crew capacity, or travel time
- Reminder and confirmation sequences to cut no-shows
- Route and job assignment logic
**Quoting and estimating**
- Intake-to-draft-quote generation from historical pricing
- Proposal assembly and e-signature flows
- Approval routing
**Knowledge and retrieval**
- RAG pipelines over a company's own documents — contracts, price lists, SOPs, spec sheets, policy manuals
- Internal assistants that give staff accurate answers instead of "ask Marc, he knows"
- Search across systems that were never designed to talk to each other
**Document and data processing**
- Invoice, receipt, PO, and contract extraction into structured data
- Intake form parsing, OCR pipelines, validation and exception handling
- Data cleaning, deduplication, enrichment, migration between systems
**Back-office operations**
- Inbox triage and drafted replies
- Invoice reminders, collections sequences, payment links
- Inventory and reorder triggers, supplier price monitoring
- Employee onboarding checklists, timesheet and payroll prep
- Compliance and reporting deadlines that currently live in someone's head
**Retention and reputation**
- Post-job review requests and response handling
- Reactivation campaigns against dormant customer lists
- Churn signals and renewal nudges
**Visibility**
- Dashboards that show owners what's actually happening: lead volume, response times, conversion, job margins, capacity
- Alerting when something breaks or a number moves the wrong way
**Integration and infrastructure**
- Connecting CRMs, accounting, field service, scheduling, and phone systems that don't natively integrate
- Custom API work where no off-the-shelf connector exists
- Deployment, monitoring, error handling, and cost control
---
#3. What I'm looking for in a developer
- **Range over specialization.** I need people who can move from a Twilio flow to a document pipeline to a dashboard without needing a new hire each time.
- **Strong Python**, plus fluency with at least one workflow platform (n8n, Make, Zapier, GoHighLevel, Activepieces).
- **API-first thinking.** Most of this work is gluing systems together well, not training models.
- **LLM application experience**: prompt design, structured output, evaluation, and knowing when an LLM is the wrong tool.
- **Vector databases** for retrieval work — Pinecone, Qdrant, Weaviate, pgvector, whatever you prefer.
- **Telephony and messaging APIs**: Twilio, Vapi, Retell, or equivalent.
- **Deployment you can hand off.** Cloud-native, documented, maintainable by someone who isn't you. I will not accept systems only one person can touch.
- **Data handling judgment.** Client data, sometimes personal or financial. You treat credentials and PII seriously.
- **French/English is a strong plus.** Many clients operate in French and their customers write in French. Not a requirement for every project, but it decides who gets certain ones.
#4. How I work
- Each project is scoped and priced on its own — hourly or fixed price per phase, your preference once scope is locked
- I handle the client relationship, requirements, and decisions; you build
- Fast approvals, no committees
- Work comes in waves as clients sign, not on a fixed schedule — be honest about your availability
- Good work gets repeat work. That's the whole model.
---
#5. To apply, answer these
1. From the list above, which categories have you actually shipped to production? Name the specific projects.
2. Which would be new territory for you, and would you take them on anyway?
3. What's your default stack for automation work, and what would make you deviate from it?
4. Describe a system you built that someone else had to maintain afterward. How did you hand it over?
5. Tell me about an automation you were asked to build that you argued against. What did you propose instead?
6. Current availability — hours per week, time zone, and how you prefer to communicate.
Start your reply with the word **BLUEPRINT** so I know you read this rather than skimmed it.
Templated proposals get ignored. Show me something you built.
HI Alexandre,
Khubaib here — solo full-stack dev/founder, I build and ship automation systems + SaaS products end-to-end. My account's still in verification so I can't DM first, putting all the stuff here.
1. Categories I've actually shipped to production:
Lead capture & response:...