Creddy.me
Collect credentials in minutes, not days
We were sick of wasting hours chasing API keys and setup info from clients... so we built something to fix it.
🚀 Just launched a new API Request module on Creddy.me
Now, in one secure link, we can collect:
🔁 Webhooks
📄 API docs & endpoints
🔐 API keys & logins
...from over 200+ SaaS tools.
This means no more:
❌ Slack threads
❌ Confused clients
❌ Back-and-forth emails
We use it to onboard new clients 10x faster especially for automation & integration projects.
🎥 Quick 30-sec demo:
https://www.tella.tv/video/streamlining-api-access-fni3
Would love your feedback and happy to share behind the scenes if anyone’s building similar flows.
🎉 First version of Creddy.me is live and we're already seeing traction!
Really glad to share that we've got the first version of Creddy.me up and running. What's even more exciting? We're already seeing other AI automation specialists starting to collect credentials through the platform!
It's one of those moments where you realize you weren't the only one struggling with this problem. Turns out, credential verification and onboarding friction is a pain point for way more people than we initially thought.
What we learned so far:
The "scratch your own itch" approach really works
Other builders in the AI space are just as frustrated with manual credential collection
There's definitely appetite for streamlined, secure verification processes
Next up:
Gathering feedback from these early users
Iterating on the UX based on real usage patterns
Adding more credential types based on demand
Big thanks to everyone who's tried it out and shared feedback. Let's gooooo!
Got tired of explaining OAuth setups to clients, so we created a directory of step-by-step tutorials for getting API keys from 200+ popular tools.
Check out r/getCredentials for the community.
The Problem Every Developer Recognizes
You know this scenario: You're integrating with a client's Salesforce, need their API credentials, and suddenly you're scheduling a screen share to walk them through their admin panel. Again.
Or you're building a Microsoft 365 integration and spending 30 minutes explaining why they need a "client secret" instead of just their password.
These aren't technical problems - they're communication problems. And they eat up way too much development time.
What We Actually Built
We started collecting step-by-step tutorials for the most common credential requests we kept having to explain.
What began as internal documentation turned into a directory of 200+ tutorials covering:
Microsoft 365 (Exchange, Teams, SharePoint, etc.)
Google Workspace (Gmail, Drive, Calendar, etc.)
Salesforce (various API types and permission levels)
HubSpot, Slack, Notion, Airtable - you name it
Each tutorial is visual, platform-specific, and written for non-technical users. Instead of explaining OAuth flows, you send a link.
How It Works in Practice
Instead of writing "Please generate an API key for your Salesforce org" and dealing with the inevitable confusion, you send a tutorial that shows:
Exactly which Salesforce menu to click
Screenshots of each step
What each field means and what to enter
How to copy the credentials correctly
Your client follows the steps, gets the credentials, and sends them back. No calls, no back-and-forth emails, no project delays.
The Developer Community Part
We started r/getCredentials because we realized other developers were solving the same problems. The subreddit has become a place to:
Share which platforms are causing the most client confusion
Request tutorials for new integrations
Discuss credential collection best practices
The directory covers most of the tools developers commonly integrate with:
CRM platforms (Salesforce, HubSpot, Pipedrive, etc.)
Email/Calendar (Microsoft 365, Google Workspace, Outlook)
Project management (Asana, Monday, Notion, Airtable)
Communication (Slack, Teams, Discord)
E-commerce (Shopify, WooCommerce, BigCommerce)
Social media (Facebook, LinkedIn, Twitter APIs)
Plus a bunch of niche B2B tools that always seem to have the most confusing credential setup processes.
The Honest Assessment
This isn't revolutionary - it's just documentation done properly. But it solves a real problem: client credential collection shouldn't take days or require phone calls or a meeting.
If you're dealing with this regularly, the directory might save you some time. If you're not, you probably don't need it.
What's the most confusing credential setup you've had to explain to a client? Drop it in r/getCredentials - we might already have a tutorial for it.
Hey fellow Indie Hackers!
I'm stepping outside my comfort zone to share a major frustration that's been driving me crazy - and I'm thinking about solving it publicly!
The Problem
As an automation specialist working with Make.com, Zapier, and n8n, I'm constantly onboarding clients who need to provide API credentials and access tokens.
This process is driving me insane:
I waste hours in meetings just walking clients through finding their API keys, client secret ID, Client ID etc.
They also send sensitive credentials scattered across email, Slack, and calls
I'm constantly explaining the same processes over and over again
It's inefficient, frustrating, and not particularly secure.
My Solution Idea
Instead of jumping straight into building a SaaS, I'm thinking of creating a collection of free, accessible tutorials that show exactly how to find and share credentials for common tools and platforms.
This could help:
Service providers like me save time onboarding clients
Clients feel more confident handling their own credentials
Everyone maintain better security practices
What about Me?
I have ADHD, which comes with its challenges, but also gives me hyperfocus periods where I become completely obsessed with solving problems I care about. Creating clear tutorials during these focus periods could be a great way to channel this energy!
For other IH members who provide services requiring client access:
What credentials do you most frequently request from clients, and for which specific tools?
Which credential collection processes frustrate you the most?
Would step-by-step tutorials showing your clients what to do be valuable to you?
I am thinking about creating a free library people can access with step-by-step tutorials. I'd love to hear your experiences before prioritizing which tutorials to create first!
Comment