Although Microsoft Flow and Nintex include many pre-built connectors for hundreds of cloud based services and apps,what if you need to integrate with a service that doesn't have a connector? This session will show how to develop custom actions using Azure Functions that can be used in MS Flow,PowerApps and Nintex Workflow Cloud.

2. Developing Azure Functions to create
custom connectors for Microsoft Flow,
PowerApps and Nintex
Tom Castiglia
DocFluix, LLC

3. AboutTom Castiglia…
SharePoint / Office 365
Consultant
Speaker at various
SharePoint
Saturday
conferences
President of the
San Diego
SharePointUser
Group
Nintex vTE
(virtualTechnical
Evangelist)
@TomCastiglia
linkedin.com/in/tomcastiglia
slideshare.net/tomcastiglia
tom@docfluix.com
meetup.com/sanspug/
meetup.com/nintexSD/
https://docfluix.com

4. Today’s Agenda
Overview
•Azure Functions
Overview
•REST Services -
Open API /
Swagger
Development
•Visual Studio 2017
•Sample Project –
Requirements
•Example Code
•Debugging
Azure
Configuration
•Azure Function
App
•Swagger Definition
Connector
Configuration
•Flow / PowerApps
•Nintex Workflow
Cloud
QuickWorkflow
demos in Flow
& Nintex using
custom
connectors

5. Prerequisites
Basics of Microsoft
Flow Basics
Basic Programming
(C# or other
languages)
Visual Studio

6. Azure Functions - Overview
Build apps faster with a serverless architecture
Accelerate your development with an event-driven, serverless compute
experience. Scale on demand and pay only for the resources you
consume.
Manage your apps instead of infrastructure
Don’t worry about provisioning and maintaining servers, especially when
your workload grows. Functions provides a fully managed compute
platform with high reliability and security and they scale on demand.

7. Azure Functions - Overview
Develop your way
• Languages: JavaScript, C#, and F#, and scripting options such as
Python, PHP, Bash, Batch, and PowerShell.
• Code directly in Azure portal
-- OR --
• Code in Visual Studio 2017 15.3 or later (Still in preview)
• Install “Azure Development” workload
• Includes tooling to create Azure Function projects and classes locally and
publish
• Includes Azure CLI (Command Line Interface) which allow you to run and debug
your functional locally.

8. Azure Functions - Pricing
Azure Functions consumption plan is billed based on per-second resource
consumption and executions. Consumption plan pricing includes a monthly
free grant of 1 million requests and 400,000 GB-s of resource consumption
per month.
METER PRICE FREE GRANT
(PER MONTH)
ExecutionTime* $0.000016/GB-s 400,000 GB-s
Total Executions* $0.20 per million 1 million
*Free grants apply to paid, consumption subscriptions only.

9. Demo
Super Quick Azure
Functions Demo

10. OpenAPI (Swagger) Overview
•When you publish an Azure Function, it creates a
REST endpoint for your function.
•OpenAPI allows you to configure the details of
your endpoint
• URL
• HTTP Methods (GET, POST, PUT, etc.)
• Inputs
• Outputs

11. OpenAPI (Swagger) Overview
•It’s a JSON file
•Configured using “YAML”…
• “a human friendly data serialization standard for all
programming languages.”
• “YAML Ain't Markup Language”
•Used by MS Flow and Nintex to import your
function as a new custom connector / action
•Help available at https://swagger.io

12. Sample Project - Goals
Accepts
complex input
types (JSON)
Does
something
useful
Returns
complex types
(JSON)

13. GSA PerDiem API
• Common workflow use cases areTravel Authorization Requests and
Expense reports, where employees travel and incur expenses for Meals and
Hotels.
• The GSA publishes official “PerDiems” that dictate the maximum amounts
that are may be expensed for Hotels and Meals.
• The PerDiem amounts are updated each year.
• Each region has its own per diems (e.g. Hotels in NYC cost more than in Des Moine)
• PerDiems also vary by month, based on peak travel seasons.
• Public web site: https://www.gsa.gov/travel/plan-book/per-diem-rates
• Often Government employees are trained to manually look up their Per Diems for
each trip prior to submitting expense reports (or better yet, before booking their
hotels)

14. GSA PerDiem API
REST API:
https://www.gsa.gov/technology/government-it-initiatives/digital-
strategy/per-diem-apis/api-for-per-diem-rates
• FiscalYear and Zip
https://inventory.data.gov/api/action/datastore_search?resource_id=8ea44
bc4-22ba-4386-b84c-
1494ab28964b&filters={"FiscalYear":"2017","Zip":“92131"}
• FiscalYear and County
https://inventory.data.gov/api/action/datastore_search?resource_id=8ea44
bc4-22ba-4386-b84c-
1494ab28964b&filters={"FiscalYear":"2017","County":"Worcester"}

15. Sample Response (abbreviated)
• The “Records” element is nested
within a bunch of stuff that can
be ignored
• The element for each month
represents the Hotel PerDiem for
that month.
• The “Meals” element represents
the PerDiem allowed for meals
for the year.

16. UsingVisual Studio
• New Project>Visual
C#>Cloud>Azure
Functions
• “Azure Functions”
maps to a “Function
App”, which can
contain 1 – N individual
functions
• Right-click the project
and select Publish
• Create new Azure
Function App. Then
click Publish.

17. Function App
• Log into Azure Portal to
review new Function App
• Notice it does not contain
any functions yet
• InVisual Studio, Right-
Click the Project and click
Add > New Azure
Function
• Name the function and
click Add
• Select function type as
HttpTrigger and click OK

18. Sample “Hello,World” Function …
Republish fromVS2017
and notice your functional
app now contains the new
function

19. GSA Per DiemWrapper
Accept Zipcode
andTripdate in
JSON as input
(in body of
request)
Validate inputs
Format REST
call to GSA API
Format JSON
response with
GSA per diem
amounts (Hotel
and Meals)

20. INPUT
JSON Formatting
OUTPUT

21. Classes for GSA Per Diem JSON

22. Deserialize Input JSON
Incoming JSON

23. Call to GSA RESTAPI

24. Output JSON / HTTP Response
JSON Response

25. Configure HTTP Methods

26. Configure API Definition

27. Export to Flow & Power Apps
Express
• Easier
• Use this if your Function App is in the same tenant as
your Flow / Office 365 AAD
Manual
• A few extra steps
• use this if yourAzure Function App is in a separate
Azure tenant.

28. Export to Flow - Express

29. Create Connection

30. Configure actions in Flow

31. NintexWorkflow Cloud

32. NintexWorkflow Cloud

33. Configure GSA Per Diem Action in NWC

34. Thank You to Our Sponsors

35. Join us right after at The Blue Prynt
Socialize and unwind after our day of learning.
Blue Prynt Restaurant & Bar
815 11th St, Sacramento, CA 95814
bluepryntsacramento.com
Thank you for joining us today!
Don’t Forget SharePint