Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More

Memberships

Alessandro's AI Community

1k members • Free

AI Infrastructure

3.1k members • Free

AI Automation (A-Z)

118.4k members • Free

Editing Incubator

452 members • Free

AI Freedom Finders

664 members • Free

AI Automation Agency Hub

274.8k members • Free

AI Automation Society

208.5k members • Free

Intelligence Artificielle

1.8k members • Free

AI Automation & Lifestyle

561 members • Free

1 contribution to AI Automation Society
How to Handle Data Privacy When Offering n8n Automation as a Service?
Hey everyone, We’re building an AI automation agency and are exploring how to integrate n8n for clients without running into data privacy issues. The main challenge: Clients need to connect their integrations (e.g., Google Sheets, CRM, Slack, etc.), but we don’t want to handle their credentials directly. We’ve considered a few options: 1. Self-hosted n8n on our infrastructure: Clients would connect their APIs via OAuth or API keys, but would they trust us with their keys? 2. Deploying n8n on the client’s infrastructure: This solves privacy concerns but makes it harder to charge a recurring fee. 3. Selling pre-built n8n templates: The problem here is that once they buy a template, they can keep using it forever, making a subscription model difficult. 4. Hybrid model: We host n8n but require clients to provide API credentials themselves. This balances privacy and usability but still has trust issues. Questions: - What’s the best way to handle authentication without compromising privacy? - Have any of you implemented a similar solution? How did you manage API access securely? - How do you ensure clients remain subscribed if selling templates? Any insights would be really helpful! Thanks in advance.
1-1 of 1
@64191137
Interested in improving my video editing skills.

Active 5d ago
Joined Feb 14, 2025
Powered by