Resolve issue reports when project tasks complete
When a task is marked complete in Motion, automatically resolve the corresponding issue in EasyCSV to maintain clean issue trackers.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
EasyCSV Explore EasyCSV →
TriggersFires when a job, build or file conversion finishes in EasyCSV.
Fires when a job, build or API request fails in EasyCSV.
Calls an EasyCSV endpoint with data from an earlier step.
Creates a PDF, image or converted file with EasyCSV.
Checks or enriches a phone number, address or IP with EasyCSV.
Motion Explore Motion →
TriggersFires when a new task, job or item is created in Motion.
Fires when a task in Motion is marked complete.
Fires when a task's due date in Motion is coming up.
Fires when a task, job or project changes status in Motion.
Creates a new task, job or item in Motion.
Updates a task's status or assignee in Motion.
Posts a comment on a task in Motion.
Assigns a task in Motion to a team member.
More EasyCSV + Motion workflows
See all EasyCSV + Motion integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Resolve issue reports when project tasks complete” between EasyCSV and Motion?
Yes — describe it in the box above and Knit's Integrations Agent researches EasyCSV and Motion's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
What's the most common Developer Tools + Project Management automation?
Marking the linked task in Motion complete (or moving it to review) automatically when a pull request merges in EasyCSV.
Does this need commit messages to reference the task ID?
That's the most reliable way to match them, though the Agent can also match on branch name or a manually linked reference depending on your workflow.