After a client accepts, InProQu can open work in the tool your delivery team already uses.
Connect the card, then accept a test document and confirm a task / card / issue appeared.
| Provider | Auth | What accept creates |
|---|---|---|
| Asana | API key | Task / project item |
| ClickUp | API key | Task in a list you configure |
| Monday.com | API key | Item |
| Trello | API key | Card |
| Jira | API key | Issue |
These are post-accept hooks. They do not replace Convert (invoice / acknowledgement still live in InProQu).
Tips
- Connect the board/list you actually work from, or the card lands in the wrong place.
- If nothing appears: the connection expired, or the document was never accepted(view is not accept).
- You can still create tasks by hand. The hook is a shortcut, not a requirement.