Transparency alternatives to IFTTT
Other Workflow automation vendors we measure, sorted by how much we found at them and not at IFTTT. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from IFTTT on at least one criterion we measured for both. Public transparency score, not a product or security rating.
IFTTT has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at IFTTT” is the one that closes them.
| Vendor | Score | Found there, not found at IFTTT | Found at IFTTT, not found there | |
|---|---|---|---|---|
| Tray.aitray.aiSee also Transparency alternatives to Tray.ai | 70/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 2 Data location stated, Public pricing | Compare |
| Zapierzapier.comSee also Transparency alternatives to Zapier | 65/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 2 Data location stated, Status page with history | Compare |
| Trigger.devtrigger.devSee also Transparency alternatives to Trigger.dev | 61/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 2 Data location stated, Status page with history | Compare |
| Pipedreampipedream.comSee also Transparency alternatives to Pipedream | 57/100 | 5 Data processing agreement, Uptime SLA with a figure, No third-party tracking before consent, +2 | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Tallyfytallyfy.comSee also Transparency alternatives to Tallyfy | 48/100 | 5 Data processing agreement, Certifications named, Uptime SLA with a figure, +2 | 2 Data location stated, Status page with history | Compare |
| Mergemerge.devSee also Transparency alternatives to Merge | 61/100 | 4 Data processing agreement, Certifications named, Notice before subprocessors change, +1 | 1 Status page with history | Compare |
| Automation Anywhereautomationanywhere.comSee also Transparency alternatives to Automation Anywhere | 52/100 | 4 Data processing agreement, Certifications named, Notice before subprocessors change, +1 | 2 Status page with history, Public pricing | Compare |
| Boomiboomi.comSee also Transparency alternatives to Boomi | 52/100 | 4 Subprocessor list, Certifications named, Uptime SLA with a figure, +1 | 1 Data location stated | Compare |
| Kissflowkissflow.comSee also Transparency alternatives to Kissflow | 52/100 | 4 Data processing agreement, Certifications named, Notice before subprocessors change, +1 | 2 Status page with history, Public pricing | Compare |
| n8nn8n.ioSee also Transparency alternatives to n8n | 43/100 | 4 Certifications named, security.txt (RFC 9116), Notice before subprocessors change, +1 | 2 Status page with history, HTTPS enforced with HSTS | Compare |
| Celigoceligo.comSee also Transparency alternatives to Celigo | 43/100 | 3 Certifications named, Uptime SLA with a figure, Named privacy contact | 1 Public pricing | Compare |
| Pipefypipefy.comSee also Transparency alternatives to Pipefy | 41/100 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.