3 ms·

Pretty different to Zapier. I'd say Zapier is very focused on piping data between different apps and tools, and is fantastic for establishing those connections.

by taaron 5y ago

Pretty different to Zapier. I'd say Zapier is very focused on piping data between different apps and tools, and is fantastic for establishing those connections. Our focus is on consolidating and running as much of the core operations and logic in a playbook or process in one platform. This means you can build, run and manage more of your operations from one centralized "command center" rather than having to glue multiple SaaS tools together to achieve the same thing. You can of course still integrate with other apps, and we actually have a Zapier integration for users who don't want to use our more technical webhook and API modules.

kungfufrog 5y ago
I have had a peruse of the product website, but I'm still kind of confused having never used a product in this niche before. When I hear "operations", as a developer/administrator I think of things like DB migrations, data archiving, crisis management, routine deploy related tasks, system and software upgrades, metrics/monitoring and associated tooling, etc. At first blush, I can't work out how a website would be particularly helpful in orchestrating those type of actions. Can you give some examples of "operations" that fall right in your wheelhouse?
- taaron 5y ago
  Sure, by "operations" we essentially mean a collection of processes which governs the right way to do something. It could be, for example, the steps you want a developer to take when making a pull request, or how a reported bug or vulnerability should be handled. For many teams, these processes are undocumented or loosely documented, so what needs to be done, in what order and when is difficult to understand, manage and scale. Workflow86 allows you to document and map out these processes with modules that can automate parts of the process (e.g. calculations, logic, sending emails, making API requests) or request human input (e.g. approvals, review, decision making). Once you've build out a process, you essentially have a functional piece of software that when started, can run that process from start to finish for you. One example that we use internally is this process for PR requests: https://app.workflow86.com/template/2b9ae31f-d29d-4198-a7b2-52a059746e85 https://app.workflow86.com/template/2b9ae31f-d29d-4198-a7b2-... Here we've taken the "checklist" which we might have otherwise stored say in Confluence, and turned it into am interactive form instead. When the form is submitted, a further checklist is assigned for the dev to complete once merged into prod. Email notifications and slack messages are automated along the way to keep the team informed. There is some logic to see if it rates as potentially risky and warning notifications accordingly. And here is another for handling data breach response: https://app.workflow86.com/template/26d48842-26cd-48bb-af51-d440cd02415b https://app.workflow86.com/template/26d48842-26cd-48bb-af51-...

by taaron 5y ago

kungfufrog 5y ago

I have had a peruse of the product website, but I'm still kind of confused having never used a product in this niche before. When I hear "operations", as a developer/administrator I think of things like DB migrations, data archiving, crisis management, routine deploy related tasks, system and software upgrades, metrics/monitoring and associated tooling, etc. At first blush, I can't work out how a website would be particularly helpful in orchestrating those type of actions. Can you give some examples of "operations" that fall right in your wheelhouse?

taaron 5y ago
Sure, by "operations" we essentially mean a collection of processes which governs the right way to do something. It could be, for example, the steps you want a developer to take when making a pull request, or how a reported bug or vulnerability should be handled. For many teams, these processes are undocumented or loosely documented, so what needs to be done, in what order and when is difficult to understand, manage and scale. Workflow86 allows you to document and map out these processes with modules that can automate parts of the process (e.g. calculations, logic, sending emails, making API requests) or request human input (e.g. approvals, review, decision making). Once you've build out a process, you essentially have a functional piece of software that when started, can run that process from start to finish for you. One example that we use internally is this process for PR requests: https://app.workflow86.com/template/2b9ae31f-d29d-4198-a7b2-52a059746e85 https://app.workflow86.com/template/2b9ae31f-d29d-4198-a7b2-... Here we've taken the "checklist" which we might have otherwise stored say in Confluence, and turned it into am interactive form instead. When the form is submitted, a further checklist is assigned for the dev to complete once merged into prod. Email notifications and slack messages are automated along the way to keep the team informed. There is some logic to see if it rates as potentially risky and warning notifications accordingly. And here is another for handling data breach response: https://app.workflow86.com/template/26d48842-26cd-48bb-af51-d440cd02415b https://app.workflow86.com/template/26d48842-26cd-48bb-af51-...