What you can connect
- Razorpay, with a key id and secret. Read-only payments and refunds.
- Stripe and Salesforce, with an API key or access token.
- GitHub, through OAuth.
- Google Drive, through OAuth, only when the server reports it as configured. If Drive app credentials are not set, the connectors page says it is unavailable instead of offering Connect.
- SQL databases, queried read-only.
- Public datasets from Kaggle, Hugging Face and OpenML.
- Your own files: CSV, spreadsheets, JSON and PDFs, uploaded into a project.
Each connector card in the app says whether it can sync live or imports a snapshot, so you know what you are getting before you connect it.
Razorpay, in detail
Generate a key in Razorpay (Account & Settings, then API Keys) and paste the key id and secret. A test-mode key works if you want to look first. The secret goes into an encrypted vault and is never shown again.
- AnalyzeIt only reads payments and refunds. It never moves money.
- It stores amounts (in rupees), status, method, bank, error code and time. It does not store customer email, phone, card or UPI details.
- The first sync looks back 90 days and reads up to 3,000 payments and 3,000 refunds; later syncs read what is new and re-check the last week, because a payment can change status after it is created.
- When you ask a question, the data is refreshed first if it has not been for 15 minutes. You can also sync from the connector card.
- If Razorpay rejects the saved keys (for example, after you regenerate them), the card says so and asks you to reconnect.
Ask “what is going wrong with my payments?” and AnalyzeIt compares failure and refund rates across method and bank and looks for the date a rate jumped. Read more in Discovery.
You decide what the assistant can read
Connected data becomes objects (tables) in a project. For each project you choose whether the assistant may read its data: ask me first, always allow, or never. You can override that per object, and “never” blocks the assistant from reading it at all.
Changes are never made silently. If you ask the assistant to update a record, it shows you a before and after and waits for your approval.
Weekly digest
Turn on a weekly check of a project's data from the Connectors screen. Each week the same analysis that answers “what is going wrong?” (or “what stands out?”) runs on the project's current data, with no language model, and is saved as a digest you can reopen. It only runs while the assistant is allowed to read the project's data. You can also have it queued by email, or to a Slack incoming webhook. Email goes out once e-mail sending is switched on for the service; until then the digest is in the app.
Live connectors such as Razorpay are also kept current on their own schedule, in addition to being refreshed when you ask a question.
Teammates
Invite people by e-mail to view a project. They accept with the address the invitation was sent to. A teammate can see the project, its charts, objects and records and the weekly digests. They cannot change anything, ask the assistant about the project, add files or connect accounts. You can remove a teammate, or withdraw an invitation, at any time. Projects can also be shared by link.
Still rolling out
- Delivery of reports to Notion.
- Teammates who can edit and not only view.
Plans and limits are on What each plan includes. If a connector you need is missing, tell us.
Want to see it rather than read about it? Try the live demo, no account needed.
Legal entity
Devansh Yadav
Sambhal, Uttar Pradesh
Governing law: Courts at Sambhal, Uttar Pradesh
Phone: +91 8433475698
Legal: legal@analyzeit.in