NiniTaxBot for Canopy firms
Designed to work with Canopy: sync your client list and bring client files from Canopy into review, then post an approved status note back.
In pilot testing
How does NiniTaxBot work with Canopy?
- Connect. Your firm creates an API key in Canopy and enters it in NiniTaxBot's settings with Canopy's API description. A person confirms which Canopy operations NiniTaxBot may use, then runs a connection test.
- Sync your client list. NiniTaxBot reads your Canopy clients into a preview showing new, changed and unchanged clients and any conflicts. Nothing changes until a person applies it. If a value differs, NiniTaxBot keeps its own and lists the difference for someone to decide. An optional schedule can check for changes and prepare a new preview, but it never applies one.
- Bring client files into review. On a linked client, choose files from that client's Canopy documents. Each one goes through NiniTaxBot's normal intake: it is stored encrypted, classified, and its values extracted. Files already brought in are recognised and not duplicated.
- Review and approve. Your team checks the extracted values beside each source document in the review queue.
- Post a status note back. When the work is ready, a person reviews and approves a short status note, which is posted to the client in Canopy.
What is sent to Canopy, and what isn't?
| Direction | What | Control |
|---|---|---|
| Read from Canopy | Your client list (names and contact fields you map) | Shown as a preview; a person applies it. SSN, TIN and date-of-birth fields are not read. |
| Read from Canopy | Files from one linked client's documents | Only that client's files, each brought in once, through normal intake |
| Sent to Canopy | A status note: status and document names only, with no amounts or identifiers | The exact text is shown and approved by a person, and the same note is never sent twice |
NiniTaxBot does not create, change or delete clients or contacts in Canopy, does not create tasks or client requests there, does not merge households, and does not delete anything. If Canopy doesn't answer clearly, NiniTaxBot doesn't resend on its own. It asks a person to check Canopy first.
How is the Canopy connection secured?
- The API key is stored encrypted with your firm's key, never displayed again, never logged, and sent only to Canopy's allowed addresses.
- Each Canopy run is recorded with who started it, the outcome and any error code. Canopy's response content is not stored in the history.
- Your Canopy plan and permissions decide what the key can do. NiniTaxBot doesn't assume access it hasn't been given.
What is the current status?
In pilot testing The Canopy integration is in pilot testing. It has not yet been checked against a live Canopy account. We'll validate it with pilot firms, using test clients, before it is used with real client data. Exports for Lacerte, UltraTax CS and Drake are coming soon.
Use Canopy? Say so on the February 2027 pilot form.
Frequently asked questions
Canopy, Lacerte, UltraTax CS and Drake are trademarks of their respective owners. NiniTaxBot is not affiliated with or endorsed by any of them. The Canopy integration is designed to work with Canopy and is in pilot testing. Lacerte, UltraTax CS and Drake exports are coming soon and are not available today.
Last reviewed: October 2026.
Spend this tax season reviewing, not retyping.
Join the CPA firms piloting NiniTaxBot in February 2027.