Copy the published post text
The Stack
copy ready · render pending
Output-policy spec format · dimensions (asset_specs.output_policy)
formatnative cut · 9:16 · 1:1 · 16:9
dims1080×1920 · 1080×1080 · 1920×1080
cadence5/day floor × 9 channels
Channels 9 destinations
TikTokInstagramLinkedInX/TwitterFacebookThreadsPinterestBlueskyYouTube
This post a distinct social asset — its own angle, storyboard, and cuts
thread-the-stack-W29-Tue
5-distinct-social/day · 9:16 master → 1:1 / 16:9 cuts per channel
Channel-cuts this asset → 9 native captions (one master · per-platform aspect+copy)
| Channel | Native caption |
|---|---|
| Tiktok | The stack: Calendly is fine for booking, but it never reads who's on the other end. So hang a webhook off the booking, pipe it to a research prompt, and walk in already knowing their stack and their likely ask. Your next meeting writes its own brief. (AI-assisted) |
| The stack: Calendly. Fine for booking. Can't read your inbox. The move: webhook off the booking pipe it to a research prompt walk in already prepared Your next meeting writes its own brief. #calendly #automation #webhooks #aitools #thestack | |
| The stack this week: Calendly, which is fine for booking and nothing more. Its limit is simple: it sets the time, but it never reads who is on the other end. The method: hang a webhook off the booking. The moment someone picks a slot, it fires their name and email to a small script that researches them. Now every call starts with you already knowing their stack, their news, and their likely ask. Add one webhook to your scheduler and pipe it to a research prompt. Your next meeting writes its own brief. | |
| X | The stack: Calendly is fine for booking, but never reads who's on the other end. Fix: hang a webhook off the booking, pipe it to a research prompt. Walk in already knowing their stack and their ask. Your meeting writes its own brief. |
| This week's stack: Calendly. It's fine for booking, but it never reads who's on the other end. So we hang a webhook off the booking, pipe it to a research prompt, and walk into every call already knowing their stack, their news, and their likely ask. Add one webhook to your scheduler and your next meeting writes its own brief. | |
| Threads | The stack: Calendly. Fine for booking. Its limit: it sets the time but never reads who's on the other end. So hang a webhook off the booking, pipe it to a research prompt, and walk in already knowing their stack and their ask. Your next meeting writes its own brief. |
| The stack: how to make Calendly do more than book a time. Its limit is that it never reads who's on the other end. The method: hang a webhook off the booking and pipe it to a research prompt, so you walk into every call already knowing their stack, their news, and their likely ask. Your next meeting writes its own brief. | |
| Bluesky | The stack: Calendly is fine for booking, but never reads who's on the other end. Fix: hang a webhook off the booking, pipe it to a research prompt. Walk in already knowing their stack. Your meeting writes its own brief. |
| Youtube | Title: Make Calendly Smarter: Auto-Brief Every Meeting With a Webhook Calendly is fine for booking, but its limit is simple: it sets the time and never reads who is on the other end. We give away the method: hang a webhook off the booking, pipe it to a research prompt, and walk into every call already knowing their stack, their news, and their likely ask. Add one webhook to your scheduler and your next meeting writes its own brief. |
Composition layer × scene 6 scenes · this post's OWN storyboard (distinct per asset)
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 | first render · fix pending shared field signature-3ddead_air | hook | 0–5.0s | kinetic-build | icon·liquid-chrome | ♪ node_lock | The tool is Calendly, fine for booking. Its limit is simple: it sets the time, but it never reads who is on the other end. on-screen: Calendly can't read your inbox |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→Calendly can't read your inbox | |||||||
| 2 |  first render · fix pending NumberedList templatedead_air | teach | 5.0–10.0s | kinetic-build | icon·white-knockout | ♪ node_lock | So we hang a webhook off the booking. The moment someone picks a slot, it fires their name and email to a small script we wrote. on-screen: Webhook to an LLM brief |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape knotground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Webhook to an LLM briefcurate items, nodes | |||||||
| 3 |  matches intent LogStream template | build | 10.0–16.6s | type-on | icon·liquid-chrome | ♪ node_lock | Now every call starts with you already knowing their stack, their news, their likely ask. You sound psychic. on-screen: Walk in already prepared |
expected on screen: red ground · a LogStream panel over a dimmed Signal Field · Magister leads · code · type-on · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id LogStreamvisual codeshape knotground redtreatment liquid-chromemotion type-onpower summoninstrument draw-on→Walk in already preparedcurate codeLines, rows | |||||||
| 4 |  matches intent KpiGrid template | proof | 16.6–22.700000000000003s | receipts-count | icon·white-knockout | ♪ node_lock | So add one webhook to your scheduler and pipe it to a research prompt. Your next meeting writes its own brief. on-screen: Add a booking webhook |
expected on screen: red ground · a KpiGrid panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id KpiGridvisual receiptsshape knotground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Add a booking webhookcurate kpis, statsLabels | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | futurist | 22.7–27.7s | spatial-parallax | icon·liquid-chrome | ♪ bed | The Stack |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldshape knotground redtreatment liquid-chromemotion spatial-parallaxpower spatial-parallaxinstrument laser-fire→The Stack | |||||||
| 6 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 27.7–32.7s | coalescence | icon·white-knockout | ♪ bed_out | The Stack |
expected on screen: red ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→The Stack | |||||||