31–40 of 63 posts
Seems like IFTTT will end up being a niche for IoT-specific integrations while this will be used for enterprise integration. What is the value here for Microsoft when you can create integrations between only competitors like Google services?
edit: "HTTP" can also be a trigger.
edit:
List of service agnostic triggers:
- Recurrence (RecurrenceTrigger an event to run at regular, customized time intervals)
- HTTP (Trigger an event based on a select REST API)
- HTTP + Swagger (Trigger an event based on a select Swagger-enabled API)
- Button (Manually trigger a flow)
- Request (This is an incoming API call that could use actions in a Logic App or other API to trigger this flow)
- RSS - When a feed item is published (Triggers a workflow when a new feed item is published)
edit:
List of service agnostic actions:
- S/FTP - Create file (This operation creates a file)
- S/FTP - List files in folder (This operation gets the list of files and subfolders in a folder)
- Delay (Set how long an action should be delayed once the flow is triggered)
- Delay until (Delay an action until a specific date. For shorter time periods, use the Delay action instead)
- HTTP (Choose a REST API to invoke)
- HTTP + Swagger (Choose a Swagger-enabled API to invoke)
- Response (This is an incoming API call that could use the results of an action to trigger this flow)
- Compose ?
- Filter Array
- Mail (Sends an email)
- Push notification - Send a push notification (Sends a push notification to the Flow app)
- RSS - List all RSS feed items (Get all RSS feed items)
- SMTP - Send Email (This operation sends an email to one or more recipients)
So like Zapier?
Should Zapier be worried ? Probably not, unless Microsoft suddenly forms a large division out of this and manages to get a 100 - 200 integrations going.
I miss Mayhem. Mayhem was an open source IFTTT-like application that ran on your own PC that Microsoft made a few years back.
This seems like a IFTTT + pipes mashup? With multiple steps, simple logic blocks, and enterprise integration.
I don't know if IFTTT should be worried –or happy– about this.
Given Microsoft's increasing emphasis on businesses, it makes sense that this is more enterprise-focused. The product itself doesn't seem much different from Apple's Automator. Microsoft's marketing of Flow, however, is better at demonstrating the product's power. Apple never quite did that.
UPDATE: it's my adblocker. It blocks a part of the page and the javascript tries to constantly load it if it fails, resulting in about 1000 errors/second in the console :)
Earlier quoted context omitted.
Yes, and that's probably why it'll be successful. There is a lot of money to be made in taking and adding enterprise integration. I mean, look at Slack. It's "merely" IRC + enterprise integration, right?
shit, my company had a "when a user is created or deleted in AD, do X" type of functionality, we could save so much freaking money money its ridiculous. Im still. planning on sitting down and building it.
Given Microsoft's increasing emphasis on businesses, it makes sense that this is more enterprise-focused. The product itself doesn't seem much different from Apple's Automator. Microsoft's marketing of Flow, however, is better at demonstrating the product's power. Apple never quite did that.
Hopefully its UI isn't as inscrutable as Automator's.