This guide helps you migrate your Zaps from the legacy Typefully Zapier integration (versions < 2.0.0) that used our old APIs to our new Zapier integration (version 2.0.0 and above)
Overview
The new Typefully Zapier integration is a complete rebuild with significant improvements. While your existing Zaps will continue to work temporarily, we recommend migrating to take advantage of new features and ensure long-term compatibility.
What's Improved
Multi-Platform Support
Legacy | New |
X (Twitter) only | X, LinkedIn, Threads, Bluesky, Mastodon |
The new integration supports all platforms that Typefully offers, letting you create cross-platform content in a single action.
Real-Time Triggers
Legacy | New |
Polling every 15 minutes | Instant triggers |
Triggers now fire immediately when events happen in Typefully — no more waiting up to 15 minutes. Our new triggers for Draft Created, Draft Deleted, Draft Status Changed, and Draft Tags Changed give you more automation options.
Enhanced Actions
Legacy | New |
Basic draft creation | Two creation methods (Simple & Advanced) |
Limited media support | Full media upload from URLs and media upload actions |
Text-only X content | Platform-specific content fields |
Steps to migrate your Zaps
Step 1: Generate a New API Key
Important: Your old API keys will NOT work with the new integration. You must generate a new one.
Click "+ New API key"
Copy and save the key securely
Step 2: Connect New Account in Zapier
In Zapier, go to My Apps or create a new Zap
Search for Typefully. Look for version 2.0.0 or above
Click "Connect a new account"
Paste your new API key
Name this connection clearly (e.g., "Typefully - New Integration")
Tip: Keep both connections temporarily so you can migrate Zaps one by one.
Step 3: Map Your Triggers
Legacy Triggers → New Triggers
Legacy Trigger | New Trigger | Notes |
When a draft is published | Draft Published | Same functionality, now real-time |
When a draft is scheduled | Draft Scheduled | Same functionality, now real-time |
(not available) | Draft Created | NEW: Fires when drafts are created |
(not available) | Draft Status Changed | NEW: Fires on any status change |
(not available) | Draft Tags Changed | NEW: Fires when tags are modified |
(not available) | Draft Deleted | NEW: Fires when drafts are deleted |
Trigger Output Field Changes
Legacy Field | New Field | Notes |
Draft content | preview | Content preview text |
Twitter link | x_published_url | Renamed for clarity |
(not available) | linkedin_published_url | NEW |
(not available) | threads_published_url | NEW |
(not available) | bluesky_published_url | NEW |
(not available) | mastodon_published_url | NEW |
share_url | share_url | Unchanged |
Step 4: Map Your Actions
Legacy Actions → New Actions
Legacy Action | New Action | Notes |
Create Draft | Create Draft Simple | For single posts with media URLs |
Create Draft (threads) | Create Draft Advanced | Use JSON for multi-post threads |
Schedule Draft | Schedule Draft | Same functionality |
Schedule Draft in Next Free Slot | Schedule Draft in Next Free Slot | Same functionality |
(not available) | Publish Draft Now | NEW: Immediate publishing |
(not available) | Upload Media by URL | NEW: Pre-upload media for Advanced action |
Field Changes
Legacy Field | New Field | Notes |
content | Platform-specific text fields | See below |
auto-split | (removed) | Use Advanced action for threads |
share | share (Generate Share URL) | Same functionality |
Publish date | publish_at | Accepts "now", "next-free-slot", or ISO datetime |
Content Field Changes
Legacy: Single content field with line breaks
First tweet of thread Second tweet of thread Third tweet of thread
New: Platform-specific fields
For Create Draft Simple (single posts):
x_text — X/Twitter content
linkedin_text — LinkedIn content
threads_text — Threads content
bluesky_text — Bluesky content
mastodon_text — Mastodon content
For Create Draft Advanced (threads):
[ {"text": "First tweet of thread"}, {"text": "Second tweet of thread"}, {"text": "Third tweet of thread"} ]
Common Migration Issues
"Invalid API Key" Error
Problem: Using the old API key with the new integration.
Solution: Generate a new API key at Settings → API.
Content Field Not Found
Problem: The legacy content field doesn't exist in new actions.
Solution: Use platform-specific fields (x_text, linkedin_text, etc.) or JSON format for threads.
Auto-Split Not Working
Problem: The auto-split option was removed.
Solution: Use "Create Draft Advanced" with JSON format for threads, or let each platform text field contain single-post content.
Missing Twitter Link Field
Problem: The field name changed.
Solution: Use x_published_url instead of twitter_link.
Testing Your Migrated Zaps
Create a test draft in Typefully
Check Zapier's Task History for the trigger
Verify all field mappings work correctly
Test each action with sample data
Compare outputs with your old Zap if needed
Cleanup After Migration
Once all Zaps are migrated and tested:
Turn off old Zaps that use the legacy integration
Delete old Zaps or archive them
Remove old Typefully connection from Zapier
Delete old API keys in Typefully social set settings
New Capabilities to Explore
Now that you've migrated, take advantage of new features:
New Triggers
Draft Created — Automate on draft creation
Draft Status Changed — Track workflow stages
Draft Tags Changed — Build tag-based workflows
Draft Deleted — Audit and cleanup automations
New Actions
Upload Media by URL → Create Draft Advanced — Build media-rich threads
Publish Draft Now — Immediate publishing for time-sensitive content
Multi-Platform Content
Post to X, LinkedIn, Threads, Bluesky, and Mastodon simultaneously
Customize content per platform for better engagement
Social Set Filtering
Filter triggers by specific accounts
Build account-specific workflows for teams or agencies