Finding Walking Time and Directions Using the ArcGIS API – FLO of the Week

Finding Walking Time and Directions Using the ArcGIS API – FLO of the Week

We’re back with FLO of the Week and focusing on something a little more complicated than our past FOTWs. This particular FLO was actually used in an application created by a team of three Azuqua employees for TechCrunch’s Disrupt London hackathon and is a bit more developer-focused than our usual FOTWs.

Wandered.space is the web app that we made for Disrupt London using Azuqua. It is a web-based service which uses your location to suggest points of interest around you to visit. It’s designed to help users explore the areas around them and find interesting locations they never would have otherwise.

Read more »

4 of the Most Interesting and Exciting APIs to Improve Your Applications

4 of the Most Interesting and Exciting APIs to Improve Your Applications

Application development today revolves around the use of APIs and the API economy.

The Web API economy is disrupting the way that organizations operate. Developers building on top of and leveraging what other developers have created to make something that they never could have done on their own. Instead of buying major products to use one small element, startups can put together their own solutions using all the different API resources available to them and make something truly specific to their needs. It’s an exciting development wonderland that enables innovation at every step of the way.

We’ve put together a list of some of the most interesting APIs available that you can use in 2017 to make amazing applications.

Read more »

December 2016 Azuqua Roundup

December 2016 Azuqua Roundup

This month, Azuqua has officially hit 80 total connectors (actually 81, to be precise)! A great way to end 2016, for sure. Just wait until you see what we have in store for 2017!

This post takes the place of FLO of the week. FOTW posts will be back on schedule next week.

Read below to learn more about the connectors released this month and other updates.

Read more »

Easily Schedule Your Workflow Integrations – FLO of the Week

Easily Schedule Your Workflow Integrations – FLO of the Week

Being able to automatically schedule your workflows is an important, underutilized aspect of workflow management. Instead of relying on people to perform mundane tasks on a consistent interval, Azuqua enables you to have FLOs triggered on any schedule that is suitable for your specific workflows.

We’ve talked about FLOs that are triggered by applications and FLOs that are triggered by other FLOs. However, we haven’t talked about what happens if you want to schedule services to run at set times instead of being triggered by something. In this case, we can build a scheduled FLO.

This week, we’re going to go over how to use the scheduled FLOs feature in Azuqua and give some examples of when it can be useful for your company.

Read more »

The Importance of Orchestrating Microservices

The Importance of Orchestrating Microservices

Microservices offer a beautiful opportunity for an enterprise to move away from monolithic architecture in favor of something that is adaptable, reliable, and scalable.

Developers are able to focus on perfecting the parts of applications that really matter instead of worrying about breaking the entire application by changing one small part of it. They’re also able to add on functionality and more microservices whenever they want to because of the general nature of the program

Customers are able to receive consistent and quick updates to an application because everything is self-reliant and can be updated easily.

Innovation is enabled through microservices architecture.

So everything’s perfect, right?

Read more »

Building Simple Microservices in Azuqua – FLO of the Week

Building Simple Microservices in Azuqua – FLO of the Week

In a development world revolving around microservices more and more, companies are finding themselves drowning in integration issues. Being able to adapt quickly and efficiently is the difference between success and failure. Most of all, these integrations need to be able to maintain agility and flexibility while the services around them change.

Azuqua serves as a fantastic platform to build and manage it all. Azuqua is able to build microservices, connect APIs, and create complex automation all through a powerful, easy-to-use visual programming language.

Today, we’re going to show you a couple of simple microservice examples built in Azuqua that we use internally every single day. Even though they’re both tiny examples and a lot simpler than what Azuqua is capable of, they serve as a good example of the microservices concept and a starting piece of knowledge for anyone to build off of.

Read more »

Onboarding Closed Deals From Salesforce to Workfront – FLO of the Week

Onboarding Closed Deals From Salesforce to Workfront – FLO of the Week

Building Workfront projects from closed deals in Salesforce is something that sounds like it should be simple and easy. However, if done manually, it becomes a time-consuming, error-prone process. Even if your team creates their own service in order to perform the process automatically, that’s still time that could have been used working on more important projects. It’s an even larger time and effort investment once something changes and the service breaks. No matter how confident you are, the hard-coded solution will always break eventually.

Instead of dealing with the trouble that hard-coding causes, Azuqua offers a platform that is agile enough to create complex microservices while keeping them stable through updates and changes to products.

Below is the process for solving this Salesforce to Workfront issue in an Azuqua FLO in order to demonstrate just how fast you could have this up and running.

Read more »

5 articles about leading digital transformation with microservice-oriented architecture & integration

5 articles about leading digital transformation with microservice-oriented architecture & integration

The importance of microservices and integration as we get closer to 2017 cannot be overstated. Survey results show that the majority of companies are converting to microservice-oriented architecture to create more integration.

This represents a major change in the way that many companies operate. Here are 5 pieces written about microservices and integration and their advantages.

Read more »

New Connectors in Azuqua: November 2016 Roundup

We have a lot of exciting new connectors that just became available on the Azuqua platform.

Wufoo

Wufoo is an incredibly easy-to-use form and survey creator. It’s now even more powerful with Azuqua because you can easily extract from any Wufoo form or even enter data into Wufoo forms.

Key Scenarios:

  • Automatically create a new row in a Google Sheet when a Wufoo form is submitted.

    wufoogooglesheetsrow

    This is incredibly useful as you can automatically update graphs as survey data is submitted.

  • Embed Wufoo forms into your mobile app

    apiendpointwufoo

    With Azuqua, you can easily link a form in your mobile app to Wufoo. Simply create a form in your mobile app that calls an Azuqua API endpoint that triggers a FLO that submits the data from your mobile app into the Wufoo form.

PagerDuty

PagerDuty is a great digital operations management system that is even greater when integrated into your technical escalation workflows with Azuqua.

Azuqua can now monitor for new incidents in PagerDuty as well as perform 11 different actions within any FLO:

pagerdutyactions

PagerDuty has many native integrations with various apps like Slack and Jira, but Azuqua lets you set up complex rules that blend all the tools at your disposal.

You can send emails to certain teams for non-urgent issues while Slacking certain individuals during the day, but SMS-ing them during off-hours. You can also keep track of incidents in any reporting tool you’d like to use such as a simple spreadsheet.

Shopify

Shopify and Azuqua make ecommerce even more powerful together. With Azuqua, you can integrate Shopify into a seamless customer experience.

Here are the new monitors (triggers that kick off FLOs) that are available:
shopifymonitors

Along with these actions (application operations taken in the middle of a FLO):
shopifyactions

Key Scenarios:

  • Unified customer experience.
    Connect your ecommerce platform with your CRM and support ticketing system so that customers never have to repeat their phone number multiple times, can get the support they need via any medium, and have a great experience the whole time.
  • Immediately responsive supply chain.
    Connect Shopify to your inventory management system or your project management systems. If a customer tries to buy something that you’re low in stock on, immediately escalate the issue to meet demand as quickly as possible by Slacking/SMSing/emailing relevant parties and triggering a new purchase workflow in your project management solution.
  • Synchronized customer data across systems.
    Make sure customer data across Shopify, email, marketing automation, CRM, ERP, and internal databases have all the right information in real-time.

Atlassian Confluence

Azuqua has connected to Jira and Hipchat since the early days, but we’re really rounding out our Atlassian portfolio with the addition of Confluence. You can now integrate Confluence into any Azuqua FLO.

You can now monitor for new or updated content in Confluence and perform these actions:
confluenceactions

Try these out for yourself at by signing up for a trial.

Mission Accomplished: FLO Force One

Mission Accomplished: FLO Force One

GE’s awesome Minds + Machines conference wrapped up this week. In addition to the conference, a Minds + Machines Hackathon was held. Azuqua sent Phill Ramey and Skyler Hartle down to the Hackathon to participate. Twenty total teams participated in the Hackathon, ranging in teams of two to teams of six.

If you want to skip reading, take a look at this video instead:

So what did Team Azuqua build? First, a bit of background.

To fully understand the depth of the solution implemented for the Hackathon, we need to briefly talk about the Predix service.

Many, Many Wind Turbines

Across the vast state of California, there are many wind turbines. Each of these turbines has a varying array of sensors that capture data about both the turbine and its surrounding environment. The data being collected from just one wind turbine is valuable. The data collected from a farm of wind turbines? That’s incredibly valuable.

Enter: Predix. Predix is a Platform-as-a-Service that is used to enable industrial internet-of-things scenarios. In our wind farm example, Predix might be used to capture and store data from these wind turbines. In essence, Predix allows you to take siloed industrial assets, connect them together, and on aggregate evaluate and analyze the data being returned from these assets.

Two of the core services that allow you to tie this all together are Predix Asset and Predix Time Series. Predix Asset lets you create a model based on a physical asset, and Time Series is a data store that allows you to store any important sensor data from an asset. Time Series acts as a historical catalogue. You can query against it in real-time, analyze it to optimize performance, or implement predictive modeling.

So let’s recap: you digitally model a physical asset in Predix using the Asset service, and you store important sensor data from assets inside the Time Series service.

In practice, there are a number of other important services that can be leveraged to provide further business value to the machines you want to connect to an industrial internet of things.

OK, that’s awesome, let’s hear about what Team Azuqua built?

Back to our wind turbine example. Let’s say that one of the turbines has started reporting an anomalous temperature sensor reading. The temperature of the turbine is far beyond what it should be, possibly indicating a mechanical failure of some sort. What do we do in this scenario? Well, let’s assume that we have service crews out in the field somewhat in proximity to the asset issuing anomalous behavior. Wouldn’t it be nice if we could dispatch a service crew to this asset, in real-time, to service the wind turbine in question?

Read more »