Step 1: Connect your account
Search for Cretask in Zapier and connect your account with an API key generated from Settings, Security. Keys are scoped to a single workspace and can be rotated or revoked without touching your password. Name the key after the Zap so you can tell later what is using it.
Step 2: Pick a trigger
Cretask emits triggers for a task created, a task completed, a status change, a new comment and a plan published. Each one carries the full task payload, including project, assignee, due date and custom fields, so the rest of the Zap has something to work with.
Step 3: Add the action
On the other side, Cretask can create a task, update one, add a note or move a task to a status. A form submission becoming a triaged task, a support ticket becoming a bug, a recurring reminder becoming a real assignment, these are all two-step Zaps.
Step 4: Test before you trust it
Run the Zap once against a throwaway project and check what actually arrives. Rate limits and errors are surfaced with the reason rather than a generic failure, and every write made through a key is attributed to that key in the task history, so a misbehaving automation is easy to find.