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
Automated YouTube Content Ideas Intake (Typeform → Slack Canvas)
Overview:
Designed and implemented an automated content intake system for the YouTube Content Ideas use-case.
New submissions are instantly structured, centralized, and made accessible to the team inside Slack Canvas — without any manual processing.
The Challenge:
Content ideas were collected via Typeform but handled through a manual workflow:
- CSV export from Typeform
- Import into Excel
- Manual formatting and structuring
- File storage and retrieval
- Recurring task to ensure updates
This created a repetitive, error-prone process tied to a single responsible person and limited real-time visibility for the team.
The Solution:
- Built a Zapier-based automation that connects Typeform with Slack Canvas and introduces a structured, low-maintenance system:
- Every new submission is automatically captured and processed
- Data is formatted into a consistent structure
- Entries are appended directly into Slack Canvas
- A scheduled notification keeps the team aligned without constant interruptions
Zap Architecture (Technical Setup):
Trigger:
Typeform → New Entry
Step 1 – Data Processing (Zapier Formatter):
- Clean and normalize inputs (text fields, formatting)
- Combine relevant fields into structured sections
- Optional: timestamp formatting for readability
Step 2 – Content Structuring:
- Build a consistent entry format (e.g. idea title, description, target audience)
- Prepare output for Slack Canvas (clean text blocks)
Step 3 – Slack Integration:
- Action: Append content to Slack Canvas
- Placement within predefined section (e.g. “New Ideas”)
- Ensures continuous, chronological documentation
Step 4 – Scheduled Notification (Zapier Schedule):
- Trigger: Every 3rd Monday
- Action: Send message to Slack channel with Canvas link
- Purpose: Batch visibility instead of constant notifications
Key Features:
- Fully automated end-to-end workflow
- Structured and centralized idea repository
- Asynchronous team visibility without notification overload
- Clean, consistent formatting of all entries
- Reliable system independent of individuals
Results & Impact:
- Removed all manual data handling steps
- Reduced operational overhead and cognitive load
- Eliminated single-point-of-failure risk
- Increased transparency and accessibility of content ideas
- Established a scalable system for ongoing content collection
Tools Used: Typeform · Zapier · Slack Canvas
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
Challenges
View all
Related posts
I explored two different approaches for the same dashboard, keeping the project, navigation, sidebar, and overall visual system consistent.
The only thing I changed was the content strategy: one version is designed around Clarity, helping users quickly understand what is happening, while the other is designed around Business Goals, focusing on outcomes, priorities, and what the business needs to achieve.
Now I’m curious which direction feels more effective for a real product.
Which design suits the best?
1 voted
100%
0 voted
0%
1 vote
Closed
Great Work
🚀 Automated AI Document Processing & ATS Pipeline (n8n)
Project Summary
Replaced a manual candidate screening process with a fully automated, n8n-orchestrated backend pipeline. The system automatically intercepts incoming applications, uses OpenAI to analyze documents, updates databases, and triggers client communication—cutting manual data entry down to zero.
The Outcome & Business Value
Eliminated Manual Data Entry: Automated 100% of resume parsing, document conversions (Docs to PDF), and data extraction tasks.
Instant Candidate Screening: Integrated an OpenAI Chat Model Decider to evaluate incoming resumes against job descriptions in real-time with zero human delay.
Automated Sync & Follow-Ups: Automated instant logging to Google Sheets and launched immediate multi-path email responses based on candidate status.
How It Works (System Architecture)
Phase 1 (Ingestion & Extraction): Captures files via webhooks/emails ➡️ Cleans data via custom code nodes ➡️ Parallel-processes files to extract raw text ➡️ Uses AI structured parsing to match applicants to open roles.
Phase 2 (Database & Delivery): Routes structured applicant data ➡️ Upserts matching rows into a centralized tracking database ➡️ Triggers dynamic conditional emails back to candidates.
Flowfolio
What it is
A Notion template for freelancers who bill through Stripe: two linked databases (Clients, Deals) with Kanban, Calendar, and List views, kept in sync automatically — when a client pays, the deal card moves itself to "Paid" instead of you dragging it by hand.
Components & how it works
The product itself lives in Notion — no separate app to log into. Deals has a Status select (Proposal → Sent → Paid / Failed / Refunded), a relation to Clients, and date/amount properties; the same data drives all three views (Board grouped by status, Calendar keyed on payment date, List sorted by value) for free, since they're just different lenses on one database.
The relay — a single Next.js API route (/api/stripe-webhook) deployed as a Vercel serverless function, on the buyer's own free Vercel account.
Event handling — Stripe's SDK (stripe.webhooks.constructEvent) verifies each request's signature before anything else runs (anything unsigned gets a 401); a small dispatcher routes four event types — checkout.session.completed, invoice.paid, invoice.payment_failed, charge.refunded — to their own handler.
Notion API (@notionhq/client) — each handler looks up the matching Deal page by its stored Stripe Invoice ID and updates its Status and Payment Date properties directly.
Idempotency — an in-memory set of processed Stripe event IDs prevents a re-delivered webhook (Stripe retries if it doesn't get a fast 200) from double-updating the same deal.
No database of its own — the relay is stateless glue between Stripe and Notion; it runs entirely inside the buyer's own Stripe, Notion, and Vercel accounts, so no third party (including the seller) ever touches their payment data.
