Tines

Our main use case for Tines is to orchestrate high-stakes data pipelines where a single broken API connection or silent error would corrupt student records. Specifically, we built an automated offboarding and data purging workflow for student accounts. When a user requested account deletion, Tines hit our internal database, pulled the user ID, and scrubbed their personal info across four different external tool APIs simultaneously. If any single API rate-limited us or timed out, Tines paused, retried with exponential backoff, and alerted our backend team via a secure webhook.

Tines offers incredible error handling capabilities. If an external API fails or blinks, Tines does not crash and burn the way simpler automation tools do. Instead, it pauses the event, saves the exact payload state, and retries automatically without losing data. Another massive advantage is how it handles webhook and HTTP requests. We do not need a pre-built app module because Tines makes working with raw APIs incredibly clean. You can easily call a command straight into the builder or auto-configure a step. For our engineering team, it meant we could build complex, multi-layered loops and conditions without guessing what was happening under the hood.

Tines has impacted our organization positively because it forced us to tighten our engineering standards around data flows. Because Tines makes you configure new raw APIs instead of hiding them behind friendly UI buttons, our team actually mapped out every single error path and edge case. During our pilot phase, it dropped our webhook error rates to zero. Whenever our external certification vendor went down for maintenance, Tines caught the failure and queued them automatically. We did not lose a single student log. It proved that we could build enterprise-grade reliability into our backend without writing a line of custom Python script. This worked as a very good infrastructure that we could base our other systems on. Having built our own custom LMS system, this helped us do proper data integration and validity checks on it.

Tines has a steep onboarding curve. If you are not a developer, there will definitely be a struggle. They need better documentation and templates for standard business apps, not just deep security tools. Building basic things takes too long. On Make.com, connecting Slack or Google Sheets takes two clicks. In Tines, we have to look up the API docs, paste the authorization header, and manually format the payload body. They should add a middle ground and give us quick pre-built connectors for the everyday SaaS stack so we do not have to reinvent the wheel for a simple notification. It is greatly useful in the case where you have your own platform running with API endpoints exposed. It helps as a good testing tool for the platform. However, for pre-existing SaaS software, it becomes a nightmare.

We bypassed Tines's AI tools entirely during our trial. When you are dealing with core infrastructure and student data pipelines, we want to be absolutely sure and not rely on any guesswork. There becomes a compliance issue with sharing student data with a platform that we are just trialing. We did not do any generative output that might hallucinate on an edge case. We mapped everything out using their hardcoded logical blocks instead. For us, reliability meant strict deterministic API paths. We never gave the AI features a chance to prove themselves one way or the other.

I have been working in the current automation field for almost four and a half to five years.

Tines is pretty stable.

Tines is quite scalable. We can use it as an enterprise app, and it scales directly without any hassle.

We never had a chance to connect with customer support.

Tines actually helped us get a better picture of what should be the workflow for error management. This, in turn, helped us build our own custom error handling tool that we are currently using with Make.com. There were other options available, but this was also just an option.

Tines required no setup cost since we just used their cloud tier and built everything with internal engineering resources. We did not need to hire an external consultant to get it running.

Tines has a steep onboarding curve. If you are not a developer, there will definitely be a struggle. They need better documentation and templates for standard business apps, not just deep security tools.

We just did a trial run with Tines, and to be quite honest, we were not exploring it for a return on investment. We did not see proper value in it, whereas other platforms would have given much higher value for us. Therefore, we shifted to use those instead.

Tines required no setup cost since we just used their cloud tier and built everything with internal engineering resources. We did not need to hire an external consultant to get it running.

We used Tines heavily for about three months during a tool evaluation phase last year. We had it running in a staging environment to see if it could handle our core infrastructure pipelines before we ultimately chose a few alternatives. One of the top competing candidates was Make.com.

My main use case for Tines has been automation. My main use has been automating simple workflows, such as moving data between tools, sending alerts, and handling routine tasks. This work gets faster and becomes much more organized.

This is the most common use case for Tines. Another use case I have utilized is automating follow-ups, such as follow-up messages after submissions. The user gets an instant reply without having to do it manually.

I think the best features Tines offers are the easy workflow builder, very strong app integrations, and real-time automations for data updates and alerts.

The workflow builder in Tines is very simple and visual. You just connect steps together as if you are building blocks. It is very easy to see what happens next, even without much coding.

What stands out mostly about Tines's features is the integrations. It connects easily with tools such as Slack, emails, and spreadsheets, and it makes data moves automatically without much work. In real-time automation, Tines is very strong and things run very instantly when an event happens, such as a form submission or an update.

Tines has impacted my organization and my work positively by making my work faster, and tasks that used to be manual now run automatically, such as data updates and alerts. It has also reduced mistakes and helped teams get updates in real-time, so that decisions can be made as soon as possible.

Tines is overall good, but the setup can feel a bit technical at first. More templates for common workflows would make it much easier to start quickly without building everything from scratch.

I can say that the documentation could be much simpler and mainly example-based, showing real workflows. Faster support responses would also help, especially when someone is building a very complex workflow so they can easily get support responses at any point.

The setup time is considerable. It takes time to set it up, and the learning curve is steep. It is not hard once you know it, but getting started takes a whole lot of time and effort and slows new users down considerably.

I will heavily dwell on a few things. More ready-made templates would help so you do not always start from scratch. A simpler onboarding flow for new users would also make it much easier to get started very quickly. Better in-app guidance when building workflows would also be helpful.

I have used Tines for roughly two years.

Tines is very stable. There have been no major downtime or issues from what I have used so far. Workflows can run very smoothly once set up. I can say that it is very stable and I prefer it over a whole lot of tools out there.

Tines can handle bigger workflows or more users easily. It scales very well. You can build bigger workflows and add more users even without breaking anything. It is built for growing teams and has more complex automation capacity. It is built for growing teams and handles much bigger and more complex automations.

I did not actually contact the support directly. However, from a whole lot of things that I saw, there were help documents and resources that were available. It is very great, and most issues were handled internally by the team.

I did not personally switch to any other tool. However, in the workflow that I work with, most processes were manual before, such as spreadsheets and normal basic emails and normal basic task handling. Tools such as Tines were then automatically introduced, and once it was introduced, we started using it to automate all these things, and we started reducing a whole lot of manual work.

The setup can feel a bit technical at first. More templates for common workflows would make it much easier to start quickly without building everything from scratch.

I actually do not work on the finance side. I do not actually know the exact ROI numbers. However, generally, it felt that times were saved on repetitive tasks, and it has saved a lot of repetitive tasks so that teams could focus more on actual work instead of just manual processes. Tines saves a whole lot of time. A whole lot of manual and repetitive tasks have been reduced, and people can now focus on something much better.

I did not handle the purchasing side, so I did not actually know the exact pricing or the licensing details. From what I saw, Tines was more of an enterprise tool. Access was already set up by the organization, and I was able to use it.

I was not actually part of the selection, so I did not actually evaluate other tools. I just started using Tines after it was already set up by the organization. However, I believe it is better than most tools out there that are used in automations.

My advice would be to start simple. The main thing is that you need to build small workflows first. When you build small workflows, you understand how it works on a bigger and more complex side. If you understand how simple automations work, then you can move into complex automations. This saves you a whole lot of time later on. The main thing is to start with simple things and then keep going.

Tines is a very solid tool overall. Once you get used to it, it makes work much easier and saves a whole lot of time. The main thing is getting comfortable with building workflows at the start. Once you understand it, it becomes much easier and you enjoy it. Tines does the job very well for automation and keeping things organized. I would rate this review an eight out of ten.

My main use case for Tines has been flexible automation. Tines also has a very strong internal engineering mindset. It is very good with respect to traditional SOAR and very flexible, and I would say it is one of the most mature and powerful automation platforms I have used so far in the market.

I use Tines for threat intelligence. I find threat intel from various sources and also implement phishing response automation. When I find phishing information, Tines helps me automatically triage it and respond to reported phishing emails, such as using report emails via Outlook add-ins, sending the indicators via emails, and enriching those emails using VirusTotal or domain reputation tools. If there is any malicious content, I proceed with it, and if it is clean, I close the case. All these activities have been completely automated using Tines. We also had a clear SOC notification embedded into this.

We also use Tines for suspicious login investigations, automating responses to risky login alerts. When someone is traveling to impossible travel locations, Tines helps us alert that to our SIEM while also using geopolitical or GeoIP location reputations. We also used it for GRC evidence collection to automate audit evidence collection for ISO 27001 and SOC 2.

Tines has positively impacted my organization because automation has brought a lot of changes, reducing a lot of effort and providing fast time to value. There are no heavy deployments; we do not have to build workflows that take a longer time. This was accomplished in minutes. ROI was immediate with huge time savings, faster onboarding, and everyone was happy to use it. Automation has spread across various organizations, not just at one particular domain in an organization, but across all areas.

In my team, the top picks for me would be API-first integration, no-code workflow builders, and audit plus control, because it was aligned with GRC controls. This has potentially saved a lot of time because I do not want to create separate evidence for running this since it was already built-in.

The percentage of improvement is at least twenty to twenty-five percent of effort that has improved. With onboarding speed, it is faster. As I said, it is almost minutes to create a workflow. In a day, I could actually have two or three workflows created just by adding APIs, and that works seamlessly. We track improvements using certain boards where we can actually track the improvements. The improvement in human versus Tines has been significant, but I cannot provide exact numbers; it has significantly improved.

The best features Tines offers are automation and flexibility. That is something which I really appreciate in Tines. There are also a lot of integrations available in Tines, which is something that should really be noted. It is more likely no-code, meaning I do not have to create any code or API-first integration. There is also a lot of automation as I mentioned, and AI Copilot workbench available so I can actually create everything within one click. An example would be resetting user passwords in Okta and executing it automatically. It also bridges the human, automation, and AI workflows. Those are some of the best features which I have actually found.

I can tell you more about the AI Copilot workbench, which helps me bridge the human, automation, and AI workflow. Natural language interaction with workflows is a standout feature. AI also assists in some of the decision-making and can trigger actions such as resetting passwords and fetching logs. If I want to reset a password in Okta, it could just execute by itself without anything required from my end. That is something which really stood out, and there is built-in case management with AI-assisted case management, which is not as heavy as traditional SOAR, but good enough for most of the SOAR workflows we have and reduces tool switching because normally we need to maintain multiple tools for the cases. This will actually be covered in this with AI Copilot.

The areas where Tines can be improved include the human, AI, plus automation model. That is something which needs real improvement, especially at the intelligent workflow layer. I think they need to add more intelligence to the workflow layer because, depending upon what they have right now, it could be possible for Claude or Copilot or ChatGPT to have that feature quickly. Those are the things they need to consider having.

I do not think user experience is a problem, but I would also say they should expand beyond security. Based on my view, I see a lot of focus on security, but Tines should not just be a security-focused solution; they should focus more on everywhere in security, not just on SecOps. The UI is great; I do not have any issues with user experience; it is very good, and they do not need to improve anything on that, at least for now.

I have been using Tines for the last one year.

Tines is stable.

Tines's scalability is pretty good. From the workloads we have, it can scale for different workflows and add more workflows, so I do not see a challenge with scalability.

The customer support is very good. I would rate the customer support a ten on a scale of one to ten.

We did not have a solution for workflow management; this is the first one.

We were able to see ROI right after implementing Tines because we observed at least twenty percent of improvements. In some domains, we were in a position to actually let go of people, meaning at least two people have been reduced from one team, which saves a lot of cost for the organization. We measure ROI based on the time it actually takes to get to market; that is something we take into consideration.

My experience with pricing, setup cost, and licensing is very good. I had a dedicated account manager available, and everything was seamless with very good discussions.

We did not evaluate other options; Tines was one of the best options we had. I had a fantastic demo with them, and that really influenced our decision to choose this platform.

My advice for others looking into using Tines is to not just look at Tines as a SOAR solution. Instead, view it more as an automation engine that amplifies whatever maturity you already have. Tines is not a detection tool; it is not even a replacement for SIEM or an EDR solution.

One thing which stood out for Tines was its flexibility, usability, and control. That is a good aspect of Tines. I would rate this review a seven out of ten.