With Wdata, you can curate data from multiple systems of record and prepare it for reporting or analysis in the Workiva platform. While you can manually upload data from external sources into Wdata tables, you can also programmatically integrate those sources with Workiva using:
Workiva's public API enables programmatic access to tables, queries, spreadsheets, and other items in Workiva solutions. Developers can use these endpoints to create custom applications and scripts to integrate Workiva with your system of record and automate the flow of data between the two.
To secure the connection to Workiva, each integration requires a dedicated Workiva user. To use the Workiva APIs, your account's administrator creates the integration users and their OAuth2 grants for authentication. Any calls to the APIs are on behalf of these users, and any historical edits show as being made by them.
Note: Using new integration users rather than existing users helps limit the access of each integration, and clearly separates edits made by actual users from those made through an integration.
In Wdata, workspace owners and other collaborators can build automated workflows—called chains—in a drag-and-drop interface to connect and manage data across multiple systems of record.
To secure this integration, chains use connectors configured with the applicable authentication and access to each source. With its connection established, each connector can enable commands to perform specific tasks as steps within a chain.
To securely interact with a system of record, each connector uses an orchestrator—or runner—to perform its commands:
- With an online cloud system, the connector uses the default CloudRunner, which operates wholly within Workiva's servers.
- With an on-premise system, the connector requires a dedicated GroundRunner, which is installed and operates within your organization's servers.
To enable a secure integration with your Workiva workspace via a chain, configure a Workiva connector. As with the Workiva API, this connector requires a dedicated integration user with an OAuth2 grant to perform its commands.