Selling data

Connectors

Every tool a company can connect, and exactly what Mora reads from each one.

A company's records already sit in the tools it works in. It connects a tool once, on that tool's own sign-in page, and its agent reads from it to build a dataset. Mora never sees a password or a token.

Two ways to read a tool

	For	The agent calls
Ready-made	The kinds of content listed below. Mora knows where the work with its outcome sits and returns it as flat records	`read_source` with the tool, where to look, and which kind of content
By path	Anything else in a connected tool	`fetch_source` with a path from the tool's own API documentation

Both only read. fetch_source sends a GET and nothing else, so an agent cannot create, change, send or delete anything in a connected tool.

Reading one

Without where, read_source says what the account holds, so the person can choose: the repositories, the projects, the channels. Then it reads one kind of content at a time, 200 records a page.

json

{ "name": "read_source", "arguments": { "tool": "github", "where": "acme/billing", "what": "reviews" } }

What comes back is raw and may name people. The agent replaces every person with a generated id before it sends anything to Mora.

Disconnecting

On the Connections page. Mora loses its access at once. Records already sent stay on the listing until the listing is deleted.

What Mora reads, tool by tool

Slack`slack`

Where to look: a channel id (the `id` in the list).

Kind	What it reads
`messages`	messages of the channel
`files`	the files shared in the channel: name, type, size, who shared it and when

Teams`microsoft-teams`

Where to look: a team id (the `id` in the list) for its channels, then that team id, a "/" and a channel id for the messages.

Kind	What it reads
`channels`	the channels of the team: id, name, what it is for, standard, private or shared
`messages`	the conversations of one channel: each message with its replies, who wrote it, when, mentions and reactions (needs "team id/channel id")

Gmail`google-mail`

Where to look: a thread id (the `id` in the list).

Kind	What it reads
`messages`	every email of the thread, in order: who wrote to whom, when, the subject and the full text
`attachments`	the files attached in the thread: name, type, size and the email each came with

Outlook`outlook`

Where to look: the word "all" for the whole mailbox, or a folder id (the `id` in the list).

Kind	What it reads
`messages`	emails with their full text, who wrote to whom and when; conversation_id ties the replies of one thread together
`events`	calendar meetings: subject, notes, start and end, who organised, who was invited and what each answered (the folder is ignored)

Dropbox`dropbox`

Where to look: a folder path such as /Reports/2025 (the `path_display` in the list), or the word "all" for every folder; for the history of one file, the path of that file.

Kind	What it reads
`files`	the files of the folder and its subfolders: name, path, size, when each was last changed
`revisions`	the history of one file: every saved version with its size and date

Google Drive`google-drive`

Where to look: the link or the id of a file or a folder.

Kind	What it reads
`comments`	review comments on the file with their replies: the passage commented, what was said, by whom, and whether it was resolved
`files`	the files inside the folder: name, type, size, description, who owns it and who changed it last
`revisions`	the history of the file: each saved version, when, by whom and its size

SharePoint`sharepoint-online`

Where to look: a site id (the `id` in the list); for the rows of one list, that site id, a "/" and the list id.

Kind	What it reads
`files`	every file and folder of the site's document library: name, folder, type, size, who created and last changed it and when
`pages`	the pages published on the site: title, summary, layout, who wrote and last changed each and when
`lists`	the lists the site holds (trackers, registers, libraries): id, name and type
`rows`	the rows of one list with every column the team filled in (needs "site id/list id")

Notion`notion`

Where to look: the link or id of a database (for its rows) or of a page (for its text and comments).

Kind	What it reads
`rows`	the rows of the database, each with all its properties (status, owner, dates, links to other rows)
`text`	the text of the page, block by block: headings, paragraphs, lists, to-dos, code
`comments`	the open comments on the page, grouped by discussion

OneDrive`one-drive`

Where to look: the word "all" for the whole drive, or the `id` of a folder or a file.

Kind	What it reads
`files`	every file and folder of the drive, or what one folder holds: name, folder, type, size, who created and last changed it and when
`versions`	the saved versions of one file: who changed it, when, and its size each time (needs the id of a file, not "all")

Confluence`confluence`

Where to look: a space id (the `id` in the list, a number).

Kind	What it reads
`pages`	pages of the space: title, full text, where it sits in the tree, who wrote and last edited it
`blogposts`	blog posts of the space: title, full text, who wrote it and when

Google Sheets`google-sheet`

Where to look: the link of a spreadsheet.

Kind	What it reads
`rows`	the rows of every tab as shown on screen, one record per row, named by the first row of the tab
`formulas`	the formulas behind the cells: where each one sits, how it is written and what it gives
`notes`	the notes people left on cells: where, what the cell holds and what the note says

Airtable`airtable`

Where to look: a base id to see its tables ("appXXX"), then base and table to read records ("appXXX/tblYYY"), then base, table and record to read its comments ("appXXX/tblYYY/recZZZ").

Kind	What it reads
`tables`	the tables of the base and the columns of each: name, type and description
`records`	the records of a table (give base and table), each with its columns, when it was created and how many comments it has
`comments`	the discussion on one record (give base, table and record): what was said, by whom, when, in reply to what

Gong`gong`

Where to look: the word "all", or a call id (the `id` in the list).

Kind	What it reads
`calls`	calls: who took part, the summary, key points, topics, and the outcome
`transcripts`	what was said in each call, turn by turn, with the speaker and the topic
`comments`	comments the team left on calls, with the moment of the call they point at

Box`box`

Where to look: the id or link of a folder (0 is the top folder) for its files; the id or link of a file for its comments, tasks and versions.

Kind	What it reads
`files`	the files and subfolders of the folder: name, description, size, who made and changed each one and when
`comments`	the comments on the file and their replies
`tasks`	the review and approval tasks on the file: what was asked, of whom, by when, and how each person answered
`versions`	the earlier versions of the file: who saved each one, when, and its size

Discord`discord-bot`

Where to look: the id or link of a channel or thread (for its messages and threads), or a server id from the list (for its channels).

Kind	What it reads
`messages`	messages of the channel or thread: text, who wrote it, what it replies to, attachments and reactions
`threads`	the closed threads and forum posts of the channel: each question with its tags and message count (read one with messages)
`channels`	the channels of a server: name, topic, type and category, to choose which to read

Zoom`zoom`

Where to look: the word "all", or a meeting id (the `id` in the list) for the full summary or the recordings of that one meeting.

Kind	What it reads
`summaries`	the written summary of each meeting: with "all" which meetings have one, with a meeting id its overview, sections and next steps
`recordings`	the cloud recordings of the last 30 days, one record per file: video, audio, chat and transcript, each with its download link

HubSpot`hubspot`

Where to look: the word "all".

Kind	What it reads
`tickets`	support tickets: what the customer asked, priority, stage, when it was closed and how it was resolved
`deals`	deals: amount, stage, whether it was won or lost and why
`emails`	emails logged on records: subject, text, direction, and the ticket or deal they belong to
`notes`	notes the team wrote on tickets, deals and contacts

Salesforce`salesforce`

Where to look: the word "all".

Kind	What it reads
`cases`	support cases: what the customer reported, priority, status, and when it was closed
`case_comments`	the comments written on cases, by the team and by customers
`emails`	emails exchanged on cases: subject, text, direction and status
`opportunities`	sales opportunities: amount, stage, next step, and whether it was won or lost

Zendesk`zendesk`

Where to look: the word "all", or a ticket id (the `id` in the list) to read the conversation of that one ticket.

Kind	What it reads
`tickets`	tickets: subject, first message, status, priority, tags, who asked, who answered and the rating given
`comments`	the conversation: every reply and internal note, in order. With a ticket id, that ticket; with "all", the oldest thousand ticket updates of the account
`ratings`	satisfaction ratings: good or bad, with the customer's comment, per ticket
`metrics`	how each ticket went: number of replies and reopens, minutes to first reply and to resolution, when it was solved

Intercom`intercom`

Where to look: the word "all", or a conversation id (the `id` in the list) to read the thread of that one conversation.

Kind	What it reads
`conversations`	conversations: the first message, state, tags, who handled it, how long it took and the rating given
`thread`	the thread of one conversation (needs its id): every reply, note, assignment and close, in order, up to the 500 most recent
`tickets`	tickets: title, description, type, state, who it is for, who handles it, and each update from open to resolved

Freshdesk`freshdesk`

Where to look: the word "all", or a ticket id (the `id` in the list) to read the conversation of that one ticket.

Kind	What it reads
`tickets`	tickets: subject, first message, status (2 open, 3 pending, 4 resolved, 5 closed), priority, tags, who asked, who answered, when it was first answered and resolved
`conversations`	the conversation of one ticket (needs its id): every reply and private note, in order
`ratings`	satisfaction ratings: the score the customer gave each ticket, with their written feedback

Front`front`

Where to look: the word "all", or a conversation id (the `id` in the list, it starts with cnv_) to read that one conversation.

Kind	What it reads
`conversations`	conversations: subject, status (open, waiting, resolved), tags, who wrote in, who it is assigned to, linked tickets
`messages`	the messages of one conversation (needs its id): every email, chat or text received and sent, with its text
`comments`	the internal comments of one conversation (needs its id): what teammates said to each other while handling it

Pipedrive`pipedrive`

Where to look: the word "all".

Kind	What it reads
`deals`	deals: value, stage, whether it was won or lost and why
`activities`	calls, meetings and tasks on deals: subject, note, whether it was done and when
`notes`	notes the team wrote on deals, people and organizations

Shopify`shopify`

Where to look: the word "all".

Kind	What it reads
`orders`	orders: what was bought, whether it was paid, shipped, delivered, returned, refunded or cancelled, and why
`products`	the catalogue: each product with its description, type, tags, status, stock and its variants with their prices

ServiceNow`servicenow`

Where to look: the word "all", or the sys_id of one record (in the list) to read the notes of that one.

Kind	What it reads
`incidents`	incidents: what was reported, how urgent, who handled it, and how it was closed (close code and resolution notes)
`notes`	the conversation on a record: every comment to the requester and every internal work note, in order. With a sys_id, that record; with "all", the latest 200 of the instance
`problems`	problems: the root cause found behind repeated incidents, the workaround and the fix
`changes`	change requests: what was changed and why, the risk, the plan, the backout plan and how it ended

Jira`jira`

Where to look: a project key (the `key` in the list, like SUP).

Kind	What it reads
`issues`	issues of the project: what was asked, its type, status, how it was resolved and when
`comments`	the discussion under each issue: who wrote what, when
`history`	every change made to each issue: status moves, reassignments, edits, by whom and when

Linear`linear`

Where to look: a team key (the `key` in the list, like ENG).

Kind	What it reads
`issues`	issues of the team: what was asked, its status, priority, who had it, when it started and when it was done
`comments`	the discussion under the issues of the team: who wrote what, when, in reply to what

GitHub`github`

Where to look: a repository as "owner/name" (the `full_name` in the list).

Kind	What it reads
`pull_requests`	pull requests, open, merged and closed: title, description, branches, who asked for review, and whether it was merged
`reviews`	review comments on pull requests: the lines of code under review, the file, and what the reviewer wrote
`issues`	issues, open and closed: the report, its labels, who took it, and how it was closed
`comments`	the discussion under issues and pull requests: who answered what, in order

Figma`figma`

Where to look: the link of a file.

Kind	What it reads
`comments`	review comments and their threads
`design`	every layer: page, frame, size, text, and the values used (colors, fonts, radius)
`versions`	the history of changes: who saved what version, when, with its label
`images`	the top frames rendered as PNG images, to send with send_files

QuickBooks`quickbooks`

Where to look: the word "all".

Kind	What it reads
`invoices`	sales invoices: what was billed, line by line, when it was due, what is still owed and the payments applied to it
`bills`	supplier bills: what was bought, on which expense account, when it is due and what is still owed
`payments`	payments received from customers: the amount, the date, and the invoices each one settled

Asana`asana`

Where to look: a project id (the `gid` in the list).

Kind	What it reads
`tasks`	the tasks of the project: what was asked, who had it, whether and when it was done
`status_updates`	the status reports written on the project: on track, at risk or off track, and the text

ClickUp`clickup`

Where to look: a workspace id (the `id` in the list).

Kind	What it reads
`tasks`	the tasks of the workspace, closed ones and subtasks included: description, status, who had it, when it was done
`time_entries`	time tracked in the last 30 days by the person who connected: which task, how long, billable or not

Trello`trello`

Where to look: a board id (the `id` in the list) or the link of the board.

Kind	What it reads
`cards`	the cards of the board, archived ones included: title, description, column, due date, whether it was completed
`activity`	what happened on the board: comments, cards created, cards moved from one column to another, cards archived
`checklists`	the checklists of the cards: each step and whether it was ticked
`lists`	the columns of the board, to read the list ids of the cards

monday.com`monday`

Where to look: a board id (the `id` in the list).

Kind	What it reads
`items`	the rows of the board with the value of every column: status, owner, dates, numbers, text
`updates`	the updates written on the rows of the board and their replies: the discussion around each piece of work
`activity`	the history of changes on the board: which value changed on which row, who changed it and when

PagerDuty`pagerduty`

Where to look: a service id (the `id` in the list), or the word "all".

Kind	What it reads
`incidents`	incidents, newest first: what broke, on which service, how urgent, who was paged, when it was resolved
`timeline`	the timeline of the incidents of the whole account, newest first: triggered, paged, acknowledged, notes written, resolved, by whom and when

GitLab`gitlab`

Where to look: a project as "group/name" (the `path_with_namespace` in the list).

Kind	What it reads
`merge_requests`	merge requests, open, merged and closed: title, description, branches, reviewers, and whether it was merged
`issues`	issues, open and closed: the report, its labels, who took it, and when it was closed
`comments`	the latest comments on issues and merge requests: who wrote what, and on which one
`pipelines`	pipeline runs: which branch and commit, what started it, and whether it passed or failed

Bitbucket`bitbucket`

Where to look: a repository as "workspace/repository", as in its Bitbucket link (the workspace is the `slug` in the list).

Kind	What it reads
`pull_requests`	pull requests, open, merged and declined: title, description, branches, and how it ended
`reviews`	what happened on pull requests: review comments with the file and line, approvals, requests for changes and updates
`pipelines`	pipeline runs: which branch and commit, what started it, how long it ran, and whether it passed or failed
`commits`	commits, newest first: the message, who wrote it and when

Sentry`sentry`

Where to look: an organization (the `slug` in the list).

Kind	What it reads
`issues`	issues of the last 90 days, resolved or not: the error, where it comes from, how often it happened, and how it was closed
`events`	error events of the last 14 days: the message, the kind of error, the files and functions it went through, and the release it happened in
`releases`	releases: the version, when it shipped, how many commits and deploys, and how many new issues it brought

Xero`xero`

Where to look: the word "all".

Kind	What it reads
`invoices`	invoices sent and bills received: line by line, the due date, what was paid, what is still owed and the day it was fully paid
`payments`	payments: the amount, the date, the invoice each one settled and whether it was matched to the bank
`bank_transactions`	money spent and received on the bank accounts: what for, how it was coded and whether it was reconciled

Stripe`stripe`

Where to look: the word "all".

Kind	What it reads
`invoices`	invoices: what was billed, line by line, and whether it was paid, voided or left unpaid, with the number of payment attempts
`payments`	payments: each charge, whether it went through, and when it failed the reason and the risk assessment
`disputes`	disputes: each chargeback, its reason, the evidence deadline and how it ended (won, lost, still open)

Connectors

Two ways to read a tool

Reading one

Disconnecting

What Mora reads, tool by tool

Slackslack

Teamsmicrosoft-teams

Gmailgoogle-mail

Outlookoutlook

Dropboxdropbox

Google Drivegoogle-drive

SharePointsharepoint-online

Notionnotion

OneDriveone-drive

Confluenceconfluence

Google Sheetsgoogle-sheet

Airtableairtable

Gonggong

Boxbox

Discorddiscord-bot

Zoomzoom

HubSpothubspot

Salesforcesalesforce

Zendeskzendesk

Intercomintercom

Freshdeskfreshdesk

Frontfront

Pipedrivepipedrive

Shopifyshopify

ServiceNowservicenow

Jirajira

Linearlinear

GitHubgithub

Figmafigma

QuickBooksquickbooks

Asanaasana

ClickUpclickup

Trellotrello

monday.commonday

PagerDutypagerduty

GitLabgitlab

Bitbucketbitbucket

Sentrysentry

Xeroxero

Stripestripe

Slack`slack`

Teams`microsoft-teams`

Gmail`google-mail`

Outlook`outlook`

Dropbox`dropbox`

Google Drive`google-drive`

SharePoint`sharepoint-online`

Notion`notion`

OneDrive`one-drive`

Confluence`confluence`

Google Sheets`google-sheet`

Airtable`airtable`

Gong`gong`

Box`box`

Discord`discord-bot`

Zoom`zoom`

HubSpot`hubspot`

Salesforce`salesforce`

Zendesk`zendesk`

Intercom`intercom`

Freshdesk`freshdesk`

Front`front`

Pipedrive`pipedrive`

Shopify`shopify`

ServiceNow`servicenow`

Jira`jira`

Linear`linear`

GitHub`github`

Figma`figma`

QuickBooks`quickbooks`

Asana`asana`

ClickUp`clickup`

Trello`trello`

monday.com`monday`

PagerDuty`pagerduty`

GitLab`gitlab`

Bitbucket`bitbucket`

Sentry`sentry`

Xero`xero`

Stripe`stripe`