Project Management
Shortcut
SaaS API (REST)
Managed auth, retries, and throttling
Export coverage
Know exactly what Vern pulls before you migrate.
Objects Vern extracts
Vern extracts the full set of queryable Shortcut objects (24 total), including: Categories, Categories Milestones, Categories Objectives, Custom Fields, Epic Workflow, Epics, Epics Comments, Epics Stories, Files, Groups, Groups Stories, Iterations, Iterations Stories, Labels, Member, Members, Milestones, Milestones Epics, Objectives, Objectives Epics, Search Epics, Stories Comments, Story History, and Workflows. 22 of these support incremental change tracking, so syncs pull only what changed.
Output schema
Normalized JSON per object with referential keys preserved, so the relationships between your user's records survive the import. Timestamps are returned in ISO 8601. Delivered as JSON or CSV, or loaded straight into your own application database or pushed to your API — whatever your product expects.
Where it can land
Your own application database (Postgres, MySQL), a direct push to your API or webhook, or JSON/CSV files, plus another project management system (Aha, Basecamp, ClickUp) when a user is switching tools.
Source details
Built for the source type shown above, with extractor content refreshed from the collection record.
Managed by Vern
The details you normally have to build yourself.
Authentication
API key / access token. Your user pastes their Shortcut API key once when they sign up; Vern stores it encrypted and attaches it to every request, handling header signing and retries so you never touch the raw credential. See Shortcut's authentication guide.
Pagination
Vern detects and handles Shortcut's paging model (cursor, page-number, or offset) internally and returns one consistent, de-duplicated result set — so you import a user's complete data without ever managing page tokens.
Rate limits and gotchas
Shortcut enforces its own API rate limits (see Shortcut's rate-limit docs). Vern queues and throttles requests internally so importing a new user's data never trips a 429 — even on a large account.
API-key sources rarely surface their true rate ceilings until you hit a 429 mid-import, and many silently cap page size. Vern throttles to stay under the limit and normalizes paging so a partial pull never lands a user in your product with missing data.
API quickstart
A cleaner way to extract without rebuilding source-specific plumbing.
View docs
Common questions
Can I keep a user's Shortcut data in sync after the first import? Yes — 22 Shortcut objects support incremental change tracking, so after the first full import Vern pulls only what changed on re-run.
Can I move a user from Shortcut to Aha? Yes — Vern normalizes the Shortcut data model into typed tables that map cleanly onto Aha and into your own product.
What does it cost to read the Shortcut API? Shortcut's own API access follows Shortcut's pricing/plan; Vern is billed separately per import. Check Shortcut's developer docs for their current limits.