Update external systems using API

Validation Form helps to make sure the post-processing is executed confidently based on data that has been verified. Let's complete the process!

Key steps in this lesson:

• Send Email to Supplier with Rejection reason and request to fix it. Use email draft from previous steps. 

• Send all Approved Invoices to Data Fabric database so that finance team can process payments via their App.

Let's configure the remaining 2 tasks in the workflow accordingly.

1. Integration Service with Gmail Connector

UiPath Integration Service is the fastest and most convenient way to automate API enabled applications. It takes care about authorization and authentication, helping you centralize management of API connections and also allowing faster integration into SaaS platforms.

Let's see what we have prepared:

There are 2 connections available: 

• shared mailbox that we can use to send emails (Gmail) 

• shared data storage where we can store any type of data (tables, files, etc)

Good part: we don't need to worry about credentials or permissions today - platform administrators have prepared these for our automation, and they are also taking care about securing and restricting access to these.

Note: make sure you are using the right tenant, or contact your trainer if there are issues with connections.

2. Data storage using Data Fabric

Great, now we know what would happen with rejected Invoices. For Invoices that have been approved, we will pass invoice data to payments team. They are using their own UiPath Automation connected to Data Fabric, so all we need to do is to push our data there.

Time to test both scenarios! Remember that the initial RPA job has an input parameter that controls probability of Invoice not matching the Purchase Order 😜