What Roiva keeps from each platform
For every platform Roiva connects to: what a sync reads, which records Roiva keeps and which of their fields, and how long it keeps them.
Answered from these docs only, by a model that cannot see your account. Check the pages it cites.
Generated from what Roiva ships, on every deploy.
What Roiva reads from each platform it connects to, and what it keeps. It's written for a security or vendor-risk review that has to answer whether Roiva holds your customers' or your staff's personal data, and where.
What a sync keeps
A sync reads the records it needs from the platform, such as tickets, deals or bills, and keeps two things:
- Records, trimmed as they're saved to the fields listed in the second table. The rest of the platform's record, such as a ticket's subject and messages, a contact's email or a customer's address, is dropped, never stored. Beside those fields Roiva keeps values it works out from them, such as a date, an amount in dollars or whether a deal was won, and, where the last column says so, a value from beyond them.
- Totals, such as a month's ticket count or spend. A platform with nothing in the second table keeps only totals.
A cost or value entry booked from a record keeps its reference, date and amount, and can keep the vendor's or customer's name. A sync's history lists the deals, customers and vendors it couldn't match to an initiative, by name. The connection itself keeps the name of what it's connected to, such as a company or workspace. For Salesforce that's the name of the person who connected it, and for Google Workspace and Microsoft 365 their email address and the names and owners of the calendars they can see. A few pickers on the link form, such as a help desk's list of agents, read names live from the platform; they're cached for up to an hour and not kept.
In your account, only Owners and Admins can open synced records. Every member sees the totals.
How long Roiva keeps it
None of it is deleted on a schedule: it's your account's data, kept while the account is. Some syncs also remove a record the platform has deleted, the next time they run.
- Disconnect stops syncing and keeps everything, including the encrypted credentials, so the connection can be brought back. For Google Workspace, QuickBooks, Slack and Xero it also asks the platform to revoke Roiva's access; for the rest, remove Roiva in the platform's own settings too.
- Delete Connection asks the same platforms to revoke Roiva's access, then deletes the connection, its credentials, its records and its sync history, except a bill an allocation rule split. The totals and the cost and value entries it booked stay on your initiatives.
- Deleting the account deletes all of it. Database backups are kept for 7 days.
Managing a connection and Your data: exports and deletion cover each step, and What each platform books covers what a record books once it's kept.
By platform
| Platform | What Roiva reads | What it keeps |
|---|---|---|
| Anthropic | Usage by model and cost by workspace for the last 12 months, and daily Claude Code usage for the last 3 months, from the Admin API. Never a prompt or a response. The Claude Code report names each user by email or API key name; Roiva adds each day up and drops the names before anything is saved. | Records of cost lines, usage by model and daily Claude Code totals, plus the totals worked out from them. |
| AWS | Daily cost by service from Cost Explorer for the last 12 months, and the same filtered by a cost-allocation tag where a link names one. | Records of daily cost by service, plus the totals worked out from them. |
| Azure | Monthly cost by service from Cost Management for the last 12 months, and the same filtered by a tag where a link names one. | Records of monthly cost by service, plus the totals worked out from them. |
| BigQuery | Job counts, bytes processed and slot time from INFORMATION_SCHEMA.JOBS, added up by month inside BigQuery, for about the last six months. Never a query's text or who ran it. Your own tables only through the metric queries you write, and from those only the period, value, entity and sample_size columns, one row per month. | Totals only, such as a month's count or spend. No record is kept. For each metric query you write, every version of its text and the rows each version returned: a month, a number, a record count, and a breakdown's value, which is whatever the query selects as its entity. These stay after the connection is deleted, because the figures computed from them point to them. |
| Brex | Card transactions posted in the last 12 months. Nothing about cardholders, and no expense reports. | Records of card transactions, plus the totals worked out from them. |
| Claude Enterprise | Daily analytics for each member for the last 3 months, of which Roiva uses only the Claude Code figures. Each row names the member by email; Roiva adds each day up and drops the names before anything is saved. | Records of daily Claude Code totals, plus the totals worked out from them. |
| Databricks | Monthly cost by product, at list price, from Databricks' system.billing tables, for the last 12 months. Never who ran a job or what it was called. Your own tables only through the metric queries you write, and from those only the period, value, entity and sample_size columns, one row per month. | Records of monthly cost by product, plus the totals worked out from them. For each metric query you write, every version of its text and the rows each version returned: a month, a number, a record count, and a breakdown's value, which is whatever the query selects as its entity. These stay after the connection is deleted, because the figures computed from them point to them. |
| Freshdesk | Tickets updated in the last 12 months, with their response and resolution times, and the IDs of deleted and spam tickets so those can be removed. Freshdesk sends each ticket's subject and requester; Roiva keeps only the fields the table below lists. | Records of tickets, plus the totals worked out from them. |
| GitHub | From the repositories the connection can see, pull requests closed and deployments made in the last 6 months, with each merged pull request's line counts; and each organization's daily Copilot totals and billing for the last 3 months. Never a pull request's description, reviews or comments. | Records of pull requests, deployments, daily Copilot totals and billing lines, plus the totals worked out from them. |
| Google Cloud | Your budgets, and monthly cost by project and service from your Cloud Billing export in BigQuery. The first sync covers 12 months and later ones the last two. Labels only where a budget filters on them. | Records of budgets, plus the totals worked out from them. |
| Google Workspace | Events on the calendars you choose, from 12 months back to the end of this month, including all-day, out-of-office and focus time. Google sends each event's title, description and attendees; Roiva keeps none of them. | Records of calendar events, plus the totals worked out from them. |
| HubSpot | Deals, contacts and tickets, all of them, with only the properties the table below lists, so never a contact's name, email or phone or a ticket's subject or content. With the optional marketing permissions, campaigns, marketing emails and blog posts from the last 12 months, and monthly website sessions by traffic source. | Records of deals, contacts, tickets, campaigns, marketing emails and blog posts, plus the totals worked out from them. |
| Intercom | Conversations created in the last 12 months. Intercom sends each conversation with its messages and the people in it; Roiva keeps only the fields the table below lists. | Records of conversations, plus the totals worked out from them. |
| Jira | Issues moved to Done in the last 3 months, with only the fields the table below lists and your site's story-point field. Never an issue's description or comments. | Records of issues, plus the totals worked out from them. |
| Looker | The saved Looks a link names, each run as the API user. Roiva keeps only each result's numbers, by month and column, and drops its text columns. | Totals only, such as a month's count or spend. No record is kept. |
| Make | Your team's scenarios and their run logs from the last 60 days. Roiva keeps run counts and credits per scenario, by name. | Totals only, such as a month's count or spend. No record is kept. |
| Microsoft 365 | Events on the calendars you choose, from 12 months back to the end of this month. Microsoft sends each event's subject, organizer and attendees; Roiva keeps none of them. Teams notifications, if you add a webhook, post the same updates as Slack. | Records of calendar events, plus the totals worked out from them. |
| n8n | Workflows, and executions from the last 12 months without their data: Roiva asks n8n to leave out what each run processed. It keeps run counts per workflow, by name. | Totals only, such as a month's count or spend. No record is kept. |
| NetSuite | Invoices and vendor bills that aren't voided, dated in the last 12 months, eight columns each; the base currency the books are kept in; monthly revenue and expense totals for the same 12 months; and the chart of accounts, departments, classes and locations. Never a line, memo, address or contact. | Records of invoices, vendor bills and income statement totals, plus the totals worked out from them. |
| OpenAI | Usage by model and cost by line item and project for the last 3 months, from the Admin API. Never a prompt or a response, and never which user or API key made a request. | Records of cost lines and usage by model, plus the totals worked out from them. |
| OpenAI Codex | Daily Codex totals for the workspace for the last 3 months. Roiva asks for workspace totals, so no developer is named in what comes back. | Records of daily usage totals, plus the totals worked out from them. |
| Pipedrive | Deals, open, closed and archived, all of them. Pipedrive sends its whole deal record; Roiva keeps only the fields the table below lists, plus any custom field a value link names. | Records of deals, plus the totals worked out from them. |
| QuickBooks | Invoices, bills, purchases and bill payments dated in the last 12 months, the profit and loss report for each of those months, and the chart of accounts, classes, locations and budgets. QuickBooks sends each document's contact details; Roiva keeps only the fields the table below lists. | Records of invoices, bills, purchases, bill payments and profit and loss reports, plus the totals worked out from them. |
| Ramp | Card transactions from the last 12 months. Ramp sends each cardholder's name and department with them; Roiva keeps neither. | Records of card transactions, plus the totals worked out from them. |
| Salesforce | Opportunities and cases, all of them, with only the fields the table below lists, plus any custom opportunity field a value link names. Never a case's subject or description, or a contact. | Records of opportunities and cases, plus the totals worked out from them. |
| Slack | The list of channels Roiva can post to. Never a message: Roiva doesn't have the permission to read them. It posts the updates you choose, such as initiative changes, approvals and notes, which name the people involved, to the channel you pick. | Nothing read from Slack. The workspace's name, the channel list, and the bot token, encrypted. |
| Snowflake | Credits used, query counts and average run times from the ACCOUNT_USAGE views, added up by month inside Snowflake, and daily spend by usage type from ORGANIZATION_USAGE, for the last 12 months. Never a query's text or who ran it. Your own tables only through the metric queries you write, and from those only the period, value, entity and sample_size columns, one row per month. | Records of daily spend by usage type, plus the totals worked out from them. For each metric query you write, every version of its text and the rows each version returned: a month, a number, a record count, and a breakdown's value, which is whatever the query selects as its entity. These stay after the connection is deleted, because the figures computed from them point to them. |
| Stripe | Successful charges from the last 12 months, each with its customer; every subscription; and, to work out tax, the invoice payments and checkout sessions from the same months, which aren't kept. Stripe sends each customer's email and address; Roiva keeps only their name. | Records of charges and subscriptions, plus the totals worked out from them. |
| Xero | Authorized and paid sales invoices and bills, and spend-money transactions, dated in the last 12 months; the profit and loss report for each of those months; and the chart of accounts, tracking categories and budgets. Xero sends each document's contact details; Roiva keeps only the fields the table below lists. | Records of invoices, bills, spend-money transactions and profit and loss reports, plus the totals worked out from them. |
| Zapier | Nothing: a step you add to a Zap posts each run to Roiva. | Records of Zap runs, plus the totals worked out from them. |
| Zendesk | Tickets created in the last 12 months, with each ticket's metrics, from Zendesk's incremental export. Zendesk sends each ticket whole, subject, description and requester included; Roiva keeps only the fields the table below lists. | Records of tickets, plus the totals worked out from them. |
Each kind of record, field by field
The fields are the ones Roiva keeps from the platform's own record; everything else in it is dropped before the record is saved. The last column names anything in those fields that can identify a person or hold free text, and anything kept beside them.
| Record | Fields kept | Names and free text |
|---|---|---|
| Anthropic cost lines | model, token_type, cost_type, amount, currency, description, workspace_id, starting_at, ending_at, context_window, service_tier | No person. Anthropic's description of each cost line, and the workspace it's in, by ID and by the name your team gave it. |
| Anthropic usage by model | model, starting_at, ending_at, uncached_input_tokens, cache_read_input_tokens, output_tokens, service_tier, context_window, workspace_id, cache_creation (ephemeral_1h_input_tokens, ephemeral_5m_input_tokens), server_tool_use (web_search_requests) | None. |
| Anthropic daily Claude Code totals | date, accepted, rejected, proposals, acceptance_rate, lines_added, lines_removed, sessions, commits, pull_requests, active_users, records_seen | None. The day's totals and a count of active users. |
| AWS daily cost by service | date, service, amount, currency, estimated | None. |
| Azure monthly cost by service | date, service, amount, currency | None. |
| Brex card transactions | id, card_id, type, description, expense_id, initiated_at_date, posted_at_date, amount (amount, currency), merchant (raw_descriptor, mcc) | The merchant's descriptor, which can name a person trading on their own, and the transaction's description. The card by Brex ID, never the cardholder. |
| Claude Enterprise daily Claude Code totals | date, accepted, rejected, proposals, acceptance_rate, lines_added, lines_removed, sessions, commits, pull_requests, active_users, records_seen | None. The day's totals and a count of active users. |
| Databricks monthly cost by product | period, product, cost | None. |
| Freshdesk tickets | id, status, priority, type, source, created_at, updated_at, responder_id, group_id, product_id, is_escalated, fr_escalated, tags, stats (first_responded_at, resolved_at, closed_at, agent_responded_at, status_updated_at) | No subject, description, requester or email address. The responding agent and group by Freshdesk ID. Tags, which are free text your team sets. |
| GitHub pull requests | id, number, repo, title, state, draft, created_at, updated_at, closed_at, merged_at, additions, deletions, changed_files, user (id, login) | The title, which is free text, and the author by GitHub ID and username. |
| GitHub deployments | id, repo, environment, production_environment, transient_environment, ref, sha, task, description, created_at, updated_at, creator (id, login) | The description, which is free text, the branch or tag, and who started it by GitHub ID and username. |
| GitHub daily Copilot totals | org, day, organization_id, code_generation_activity_count, code_acceptance_activity_count, loc_suggested_to_add_sum, loc_added_sum, daily_active_users, weekly_active_users, monthly_active_users, user_initiated_interaction_count | None. Totals for the organization, not for any one person. |
| GitHub billing lines | organizationName, org, date, product, sku, repositoryName, unitType, quantity, pricePerUnit, grossAmount, discountAmount, netAmount | None. |
| Google Cloud budgets | name, displayName, etag, amount (specifiedAmount (currencyCode, units, nanos)), thresholdRules (thresholdPercent, spendBasis), budgetFilter (calendarPeriod, creditTypesTreatment, projects, services) | No person. The budget's name and its whole filter, including any labels it filters on, which your team chose. |
| Google Workspace calendar events | id, status, created, updated, recurringEventId, eventType, recurrence, start (dateTime, date, timeZone), end (dateTime, date, timeZone), attendees (responseStatus, organizer, self, optional, resource), conferenceData (conferenceSolution (name)) | No title, description, location or attendee. When an event was, how long it ran, how many were invited and accepted, and whether it recurred or was online. Which of your chosen calendars it was on, and a person's calendar ID is their email address. |
| HubSpot deals | id, createdAt, updatedAt, archived, properties (dealname, dealstage, amount, closedate, createdate, pipeline, hubspot_owner_id, hs_object_id, hs_lastmodifieddate) | The deal's name, which often names the customer, and its owner by HubSpot user ID. The value of any custom property a value link is set to match on. A value entry booked from a won deal keeps its name. |
| HubSpot contacts | id, createdAt, updatedAt, archived, properties (lifecyclestage, createdate, hs_lead_status, leadsource, hs_object_id, lastmodifieddate) | No name, email or phone. One record per contact, identified by its HubSpot ID, with its lifecycle stage and lead source. |
| HubSpot tickets | id, createdAt, updatedAt, archived, properties (hs_pipeline_stage, createdate, closed_date, hs_ticket_priority, source_type, hs_object_id) | None. No subject, content or requester. |
| HubSpot campaigns | id, createdAt, updatedAt, properties (hs_start_date, hs_end_date, hs_name) | The campaign's name. |
| HubSpot marketing emails | id, name, publishDate, stats (counters (delivered, open)) | The email's internal name. No subject, content or recipients. |
| HubSpot blog posts | id, publishDate, state, created, updated | None. No title, content or author. |
| Intercom conversations | id, state, open, priority, created_at, updated_at, admin_assignee_id, team_assignee_id, ai_agent_participated, source (type, delivered_as), statistics (time_to_admin_reply, time_to_first_close, count_reopens, count_assignments, count_conversation_parts, first_close_at, last_close_at), conversation_rating (rating, created_at), tags (tags (id, name)) | No message, author, contact or rating comment. The assigned teammate and team by Intercom ID. Tag names. |
| Jira issues | id, key, fields (summary, created, resolutiondate, statusCategoryChangedDate, assignee (accountId), issuetype (id, name), status (id, name, statusCategory (key)), priority (id, name)) | The issue's summary, which is free text. Its assignee by Atlassian account ID, never a name or email. |
| Microsoft 365 calendar events | id, isAllDay, isCancelled, isOnlineMeeting, start (dateTime, timeZone), end (dateTime, timeZone), attendees (type, status (response)), recurrence (pattern (type, interval)), responseStatus (response) | None. No subject, organizer or attendee. When an event was, how long it ran, how many attended and responded, and whether it recurred or was online. |
| NetSuite invoices | id, tranid, trandate, foreigntotal, foreignamountunpaid, exchangerate, currency, entity_name | The customer's company name, on every invoice. A value entry booked from an invoice keeps it. |
| NetSuite vendor bills | id, tranid, trandate, foreigntotal, foreignamountunpaid, exchangerate, currency, entity_name | The vendor's company name. |
| NetSuite income statement totals | The month's revenue and expense totals, which Roiva's query adds up inside NetSuite. | None. |
| OpenAI cost lines | object, line_item, project_id, start_time, end_time, amount (value, currency) | No person. The project it's billed to, by ID and by the name your team gave it. |
| OpenAI usage by model | object, model, start_time, end_time, input_tokens, output_tokens, input_cached_tokens, input_audio_tokens, output_audio_tokens, num_model_requests, project_id, batch | None. |
| OpenAI Codex daily usage totals | object, start_time, end_time, totals (threads, turns, credits, cost_usd, estimated_cost_usd, uncached_text_input_tokens, cached_text_input_tokens, text_output_tokens, text_total_tokens), code_attribution (lines_of_code (added, removed, committed, total_committed_lines, committed_percentage)) | None. |
| Pipedrive deals | id, title, value, currency, status, pipeline_id, stage_id, owner_id, probability, is_archived, is_deleted, add_time, update_time, close_time, won_time, lost_time, expected_close_date | The deal's title, which often names the customer, and its owner by Pipedrive user ID. The value of any custom field a value link is set to match on. A value entry booked from a won deal keeps its title. Not the person or organization the deal is with. |
| QuickBooks invoices | Id, DocNumber, TxnDate, TotalAmt, HomeTotalAmt, ExchangeRate, CurrencyRef (value, name), DepartmentRef (value, name), MetaData (CreateTime, LastUpdatedTime), TxnTaxDetail (TotalTax), LinkedTxn (TxnId, TxnType), Line (Id, LineNum, Description, Amount, DetailType, AccountBasedExpenseLineDetail (AccountRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), ItemBasedExpenseLineDetail (Qty, UnitPrice, ItemRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), SalesItemLineDetail (Qty, UnitPrice, ItemRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), LinkedTxn (TxnId, TxnType)), DueDate, Balance, HomeBalance, CustomerRef (value, name) | The customer's name on every invoice, whether or not an initiative uses it. If you invoice individuals, that's a person's name. Each line's description, which is free text. A value entry booked from an invoice keeps the customer's name. No email, address or phone. |
| QuickBooks bills | Id, DocNumber, TxnDate, TotalAmt, HomeTotalAmt, ExchangeRate, CurrencyRef (value, name), DepartmentRef (value, name), MetaData (CreateTime, LastUpdatedTime), TxnTaxDetail (TotalTax), LinkedTxn (TxnId, TxnType), Line (Id, LineNum, Description, Amount, DetailType, AccountBasedExpenseLineDetail (AccountRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), ItemBasedExpenseLineDetail (Qty, UnitPrice, ItemRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), SalesItemLineDetail (Qty, UnitPrice, ItemRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), LinkedTxn (TxnId, TxnType)), DueDate, Balance, HomeBalance, VendorRef (value, name), APAccountRef (value, name) | The vendor's name, which can be a person trading on their own, and each line's description. No address or contact details. |
| QuickBooks purchases | Id, DocNumber, TxnDate, TotalAmt, HomeTotalAmt, ExchangeRate, CurrencyRef (value, name), DepartmentRef (value, name), MetaData (CreateTime, LastUpdatedTime), TxnTaxDetail (TotalTax), LinkedTxn (TxnId, TxnType), Line (Id, LineNum, Description, Amount, DetailType, AccountBasedExpenseLineDetail (AccountRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), ItemBasedExpenseLineDetail (Qty, UnitPrice, ItemRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), SalesItemLineDetail (Qty, UnitPrice, ItemRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), LinkedTxn (TxnId, TxnType)), PaymentType, Credit, AccountRef (value, name), EntityRef (value, name, type) | The payee's name and type, which can be an employee or a customer, and each line's description. |
| QuickBooks bill payments | Id, DocNumber, TxnDate, TotalAmt, HomeTotalAmt, ExchangeRate, CurrencyRef (value, name), DepartmentRef (value, name), MetaData (CreateTime, LastUpdatedTime), TxnTaxDetail (TotalTax), LinkedTxn (TxnId, TxnType), Line (Id, LineNum, Description, Amount, DetailType, AccountBasedExpenseLineDetail (AccountRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), ItemBasedExpenseLineDetail (Qty, UnitPrice, ItemRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), SalesItemLineDetail (Qty, UnitPrice, ItemRef (value, name), ClassRef (value, name), TaxCodeRef (value, name)), LinkedTxn (TxnId, TxnType)), PayType, VendorRef (value, name), CreditCardPayment (CCAccountRef (value, name)), CheckPayment (BankAccountRef (value, name)) | The vendor's name, and the name of the bank or card account that paid. |
| QuickBooks profit and loss reports | The month's profit and loss report as QuickBooks returns it: account rows and totals, with no customer or vendor breakdown. | None. |
| Ramp card transactions | id, state, amount, currency_code, card_id, merchant_name, merchant_descriptor, merchant_category_code, memo, user_transaction_time, synced_at | The merchant's name and descriptor, and the memo, which is free text the cardholder writes. The card by Ramp ID, never the cardholder. |
| Salesforce opportunities | Id, Name, StageName, Amount, CloseDate, CreatedDate, OwnerId, Type, Probability, attributes (type) | The opportunity's name, which often names the customer, and its owner by Salesforce user ID. The value of any custom field a value link is set to match on. A value entry booked from a won opportunity keeps its name. |
| Salesforce cases | Id, CaseNumber, Status, Priority, Origin, Type, CreatedDate, ClosedDate, AccountId, OwnerId, attributes (type) | No subject, description or contact. The customer's account and the case owner by Salesforce ID only. |
| Snowflake daily spend by usage type | usage_date, usage_type, currency, usage_in_currency | None. |
| Stripe charges | id, object, status, amount, amount_captured, amount_refunded, currency, customer, description, invoice, payment_intent, paid, captured, refunded, created | The customer's name, or the cardholder's when the customer has none. If you sell to individuals, that's a person's name. The charge's description. A value entry booked from a charge keeps the customer's name. No email, address or card details. |
| Stripe subscriptions | id, object, status, currency, customer, created, canceled_at, cancel_at_period_end, current_period_start, current_period_end, items (data (id, quantity, price (id, unit_amount, currency, product, recurring (interval, interval_count)))) | None. The customer by Stripe ID only. |
| Xero invoices | Type, InvoiceID, InvoiceNumber, Reference, Status, Date, DueDate, LineAmountTypes, CurrencyCode, CurrencyRate, SubTotal, TotalTax, Total, AmountDue, AmountPaid, AmountCredited, FullyPaidOnDate, UpdatedDateUTC, Contact (ContactID, Name), LineItems (LineItemID, Description, Quantity, UnitAmount, LineAmount, ItemCode, AccountCode, AccountID, TaxType, TaxAmount, Tracking (TrackingCategoryID, TrackingOptionID, Name, Option)), Payments (PaymentID, Date, Amount, Reference, CurrencyRate) | The customer's name on every invoice, whether or not an initiative uses it. If you invoice individuals, that's a person's name. The reference, each line's description and each payment's reference, which are free text. A value entry booked from an invoice keeps the customer's name. No email, address or phone. |
| Xero bills | Type, InvoiceID, InvoiceNumber, Reference, Status, Date, DueDate, LineAmountTypes, CurrencyCode, CurrencyRate, SubTotal, TotalTax, Total, AmountDue, AmountPaid, AmountCredited, FullyPaidOnDate, UpdatedDateUTC, Contact (ContactID, Name), LineItems (LineItemID, Description, Quantity, UnitAmount, LineAmount, ItemCode, AccountCode, AccountID, TaxType, TaxAmount, Tracking (TrackingCategoryID, TrackingOptionID, Name, Option)), Payments (PaymentID, Date, Amount, Reference, CurrencyRate) | The supplier's name, which can be a person trading on their own, the reference, and each line's description. No email, address or phone. |
| Xero spend-money transactions | Type, BankTransactionID, Reference, Status, Date, LineAmountTypes, IsReconciled, CurrencyCode, CurrencyRate, SubTotal, TotalTax, Total, UpdatedDateUTC, Contact (ContactID, Name), BankAccount (AccountID, Code, Name), LineItems (LineItemID, Description, Quantity, UnitAmount, LineAmount, ItemCode, AccountCode, AccountID, TaxType, TaxAmount, Tracking (TrackingCategoryID, TrackingOptionID, Name, Option)) | The payee's name, which can be a person, such as an employee paid back, the reference, and each line's description. |
| Xero profit and loss reports | The month's profit and loss report as Xero returns it: account rows and totals, with no customer or supplier breakdown. | None. |
| Zapier Zap runs | run_id, zap_id, zap_name, status, occurred_at | The Zap's name, which your team chose. Anything else the step posts is dropped. |
| Zendesk tickets | id, status, type, priority, created_at, updated_at, assignee_id, group_id, brand_id, ticket_form_id, tags, via (channel), satisfaction_rating (score), metric_set (solved_at, reply_time_in_minutes (calendar, business)) | No subject, description, requester or satisfaction comment. The assignee, group and brand by Zendesk ID. Tags, which are free text your team or your triggers set. |