Common Connectors & Notable Nodes in Chains
Exploring Chains? Here are some Common Connectors and Notable Nodes that we think you should check out!
Common Connectors
Workiva Connector: Commands to interact with Workiva
You can use this connector and its commands to share Workiva data externally, share Workiva data within Workiva, and automate different actions within the platform. If you are often doing manually tasks in Workiva, it could be worthwhile to see if using the Workiva Connector can help with efficiency and accuracy.
A few common commands you can perform with the Workiva Connector:
- Get data from a Spreadsheet or Write data to a Spreadsheet
- Run a Query and get data results of a Query
- Create and Upload a file to a Wdata Table
- Refresh a connection or list of connections
HTTP Request Connector: Performs HTTP requests to execute Workiva and other system APIs
If Workiva does not have an out-of-the connector for a system you would like to connect to, you can use the HTTP Connector to establish a connection. You can think of this as a catch all or placeholder connector that can be used with almost any platform that supports HTTP/HTTPS connectivity.
Common commands performed with HTTP request:
- GET
- POST
SFTP Connector: Access and modify files saved on an SFTP Server
If you would not like to have a direct connection to an external system, the SFTP connector is another way to automate bringing data into the Workiva platform.
Common commands performed with the SFTP Connector:
- List Directory
- Get File
- Download File
- Delete File
File Utilities Connector: Commands to access and manage files and directories on Microsoft Windows and Linux-based operating systems
Common Commands performed with File Utilities:
- List Directory and retrieve a File
- Create, Copy, Delete files
- Zip or Unzip files
Notable Nodes
Trigger Event: Runtime Inputs specify the value of variables that are used throughout a Chain at the time of execution. This node is somewhat of a form structure and allows Chains to be more dynamic. Each chain can be executed multiple times with different values input at the execution time. You can say “Run through this process for System 1” and then “Run through this process for System 2” and even have them run concurrently if needed.
Chain Event: Run Chain allows you to kick off a Chain as a step within another Chain. This allows you to reference other processes so you do not have to rebuild or re-invent the wheel within your original Chain.
Chain Event: Runtime File Upload allows you to manually upload a file during Chain execution. If you are not connected to any systems, or would just like to have a quick and easy way to upload a file this is a nice option to do so. This node kicks off an email to an uploader or uploaders with details and a time frame for uploading. Once they complete their task, the Chain continues on.
-
This is really helpful, thank you for laying this out.
In my experience, the SFTP connector is often the go-to for companies moving data from source systems like ERPs into Workiva. While some see SFTP as outdated, it usually strikes the right balance of flexibility, security, and ease of setup.
For example, a common setup I’ve seen for SEC and Sustainability reporting teams is ERP → nightly export to SFTP → Workiva Chain picking up the file and loading it into Wdata tables. It avoids the complexity of a direct API build while still giving teams reliable, governed automation.
0U moet u aanmelden om een opmerking te plaatsen.
Opmerkingen
1 opmerking