Arbor Workflows: Document step

Arbor Workflows’ Document step integrates with Google Drive or SharePoint to save generated and uploaded PDFs. It automatically creates workflow folders, supports multiple documents and up to three dynamic subfolders, and lets users test folder creation and uploads before running workflows.

 

Great we’re authenticated Google or Microsoft within your School Settings area as detailed in this article: Arbor Workflows x Google Drive → how do I build the integration in Arbor Workflows?

Our new Document step (previously known as Storage) can use this integration to deposit documents created or collected by the Workflows into a Google Drive or Sharepoint folder. Let’s use an example to understand what is possible. We are going to add a Google Drive integration to one of our workflows powering recruitment, Staff Onboarding.

As a part of this process, the new staff member completes an initial form. You’ve chosen for Arbor Workflows to generate a PDF of this form, but now need to save this document to a folder.

Within the workflow editor, we choose to upload a file to Google Drive via the Document Step.

We select the Document step via the dropdown. Upon doing so, Workflows will automatically create a new folder within your Arbor Workflows folder for this workflow. The name will match your workflow’s name.

Great! So Workflows will now upload all relevant documents to this folder as workflows run.

Within the Documents to send area, any PDFs that are available from the workflow will be available to select. This will include PDFs of steps that have been set up to produce a PDF and documents uploaded into the workflow via a form step. 

Select the documents you wish to be saved to the folder from the dropdown. A key difference on the Document step versus the previous Storage step is that multiple documents can now be saved to the folder within a single step. 

How do I set my folders up?

You might choose for Arbor Workflows to create three folders within your workflows Staff Onboarding folder. Inside this folder, you choose to create the following:

  • Folder with the school they will work at (let’s imagine you are part of a MAT). You can select the dynamic data to pull this through.

  • Department they work in (let’s imagine using their Head of Department name for this).

  • Name of the new starter 

Build up to three dynamic folders → Arbor Workflows will create or use these folders as the workflow runs.

 

How can I test this integration?

Once you’ve built your Google Drive integration, you can test to this within the Review & Test area, testing the workflow in the usual way. Find out how here: Arbor Workflows: Testing a Workflow.

By doing this, you will see the folder structure that Arbor Workflows will create for you. When the workflow runs, we will use the actual data (school name, department and name). At this point, we will just use these placeholders to test the folder creation and file upload.

After testing the workflow,  feel free to delete these to keep your folder tidy.

Was this article helpful?
0 out of 0 found this helpful
I'm still stuck!

Comments

0 comments

Please sign in to leave a comment.