The connector only reads data. It never creates, changes or deletes anything in FlyUp BPO.
Configuring FlyUp BPO as a Source
In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the FlyUp BPO option from the list of connectors. Click Next and you’ll be prompted to add your access.1. Add account access
The connector signs in with the email and password of a FlyUp BPO user, the same ones used to sign in to the FlyUp BPO web app. It sees exactly what that user sees: a company user sees its own company (or companies), and a FlyUp BPO operator sees the companies assigned to them. We recommend a user created for Nekt, so that a password change by a person does not stop your syncs. The following configurations are available:- Email: Email of the FlyUp BPO user.
- Password: Password of that user.
- Client IDs (advanced, optional): Comma-separated identifiers (UUIDs) of the FlyUp BPO companies (clients) to sync. Leave it empty to sync every company the user can see. You can find the identifiers in the
idcolumn of the Clients table after a first sync. Every identifier must be a company this user can see, otherwise the sync stops with a message naming it. Plan Groups, Proposals and Contracts don’t belong to a company, so they are always synced in full.
2. Select streams
Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.Tip: The stream can be found more easily by typing its name.Select the streams and click Next.
3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.- Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
- Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
- Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
- Sync Type: every FlyUp BPO stream is FULL_TABLE: every time the extraction happens, we get the current state of the data, so records deleted in FlyUp BPO also leave your catalog.
4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here. Once you are ready, click Next to finalize the setup.5. Check your new source
You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.Streams and Fields
Available streams
The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description.Fields by stream
Financial entries and cash
Transactions
Transactions
Financial entries: payables, receivables and realized cash movements (cash flow).Table:
transactions · Primary key: id · Sync: Full tableScheduled Transactions
Scheduled Transactions
Scheduled entries: installment plans, recurrences and single future entries.Table:
scheduled_transactions · Primary key: id · Sync: Full tableBank Accounts
Bank Accounts
Bank accounts (and cards, gateways, marketplaces) of each client, with the current balance.Table:
bank_accounts · Primary key: id · Sync: Full tableBank Account Balance History
Bank Account Balance History
Monthly balance history per bank account: realized and forecast debits and credits.Table:
bank_account_balance_history · Primary key: id · Sync: Full tableBank reconciliation
Conciliations
Conciliations
Bank reconciliations: one per imported bank statement (OFX, Excel, PDF, Open Finance or manual).Table:
conciliations · Primary key: id · Sync: Full tableImported Transactions
Imported Transactions
Bank-statement lines imported for reconciliation, with their reconciliation status.Table:
imported_transactions · Primary key: id · Sync: Full tableIncome statement and planning
DRE (Income Statement)
DRE (Income Statement)
Income statements (DRE) stored by FlyUp BPO per client, period and unit.Table:
dre · Primary key: id · Sync: Full tableFinancial Goals
Financial Goals
Yearly financial goals (budget) per client, with pessimistic, realistic and optimistic scenarios.Table:
financial_goals · Primary key: id · Sync: Full tableFinancial Plans
Financial Plans
Financial plans (planned values per scenario) of each financial goal.Table:
financial_plans · Primary key: id · Sync: Full tableScenario Analyses
Scenario Analyses
What-if scenario analyses (desired margin, average price) per client and year.Table:
scenario_analyses · Primary key: id · Sync: Full tableCompanies and registries
Clients
Clients
FlyUp BPO clients (the companies whose finances are managed) visible to the source’s user.Table:
clients · Primary key: id · Sync: Full tableUnits
Units
Business units (branches) of each client.Table:
units · Primary key: id · Sync: Full tableCustomers and Suppliers
Customers and Suppliers
Customers and suppliers (pessoas) used in the financial entries.Table:
persons · Primary key: id · Sync: Full tableProjects
Projects
Projects (cost centers) of each client.Table:
projects · Primary key: id · Sync: Full tablePlan Groups
Plan Groups
Top level of the chart of accounts: groups and how they enter the income statement (DRE).Table:
plan_groups · Primary key: id · Sync: Full tablePlan Categories
Plan Categories
Second level of the chart of accounts: categories inside each group, per client.Table:
plan_categories · Primary key: id · Sync: Full tablePlan Subcategories
Plan Subcategories
Third level of the chart of accounts: the subcategories financial entries are classified in.Table:
plan_subcategories · Primary key: id · Sync: Full tableProposals and contracts
Proposals
Proposals
Commercial proposals sent from FlyUp BPO.Table:
proposals · Primary key: id · Sync: Full tableContracts
Contracts
Contracts generated from FlyUp BPO and their signature status.Table:
contracts · Primary key: id · Sync: Full tableImplementation notes
- Full table streams. FlyUp BPO’s lists have no “updated since” filter, so every table is read in full on every sync. Each table is read completely before it is loaded: if the read fails halfway, the table keeps its previous data and the sync shows the error.
- Amounts. FlyUp BPO stores money as whole numbers, and the connector loads them exactly as FlyUp BPO returns them, without a decimal separator. Compare a few values with the FlyUp BPO app before building reports (most likely they are in cents, so divide by 100).
- Which company a row belongs to. Financial entries, scheduled entries and financial plans don’t say which company they belong to, so the connector reads them company by company and fills
client_id. A row that does not show up under any company the user can see is still loaded, withclient_idempty. If the list of companies cannot be read because of a temporary error, those tables fail in that sync instead of loading withoutclient_id. - First sync check. After the first sync, compare the number of rows in Transactions (per company,
client_id) with the number of entries FlyUp BPO shows for the same company, to confirm the user sees everything you expect. - Related records in entries. In Transactions and Scheduled Transactions, the subcategory, customer/supplier, project, bank account and unit come as
*_name(as FlyUp BPO displays them) and*_idwhen FlyUp BPO returns the identifier. - Income statements. The DRE table brings the income statements FlyUp BPO has stored, with their lines and values in the
datacolumn (JSON). It does not ask FlyUp BPO to compute new ones. - Permissions. Before reading anything, the connector checks that the user can read every table you selected. A table the user is not allowed to read, or that FlyUp BPO does not have for your account (a module that is not enabled), is skipped with a warning naming it and saying which of the two happened, and the other tables still load; if the user cannot read any selected table, the sync fails with a message.
- Rate limits. If FlyUp BPO asks the connector to slow down, the sync waits and continues, and says so in the sync log.