Act on events from another service
Get a private address that another service (a form tool, a delivery app, a calendar) sends its updates to. DontCode checks each one is genuine and saves it, and your app acts on it: a new row, an email, a status change.
The problem this solves
Your tools know things your app should know: a form was filled, an order shipped, a meeting was booked. Copying them over by hand is slow and error-prone, and building a receiver yourself means servers, signatures and retries.
What you end up with
One private address per service. Every update is checked and recorded, so you can see what came in and when, and your app does what you described in plain words, like 'when a Typeform response arrives, add a lead and email me'.
How it works
- You add the service once and get a private address for it.
- You paste that address into the other service's settings.
- Each update it sends is checked as genuine and recorded.
- Your app does what you described: save it, email someone, change a status.
- Updates that can't be handled are kept, so nothing is lost.
Build this in your app
Build this in your appInsight asks a few questions first, so it fits your app.
Built from
Inbound webhook receiver
IntegrationsGet a private web address that outside services can send events to. DontCode checks that each message is genuine, records it, and passes it to your live app. You describe, in plain words, what should happen when an event arrives.
Integration credentials (encrypted env vars)
IntegrationsStore the login keys for your outside services (keys, secrets, tokens). They're encrypted the moment you add them and can never be read back as plain text. Your live app uses them securely, without the keys ever appearing in your code.
Data, your live rows like a spreadsheet
DatabaseSee and edit your app's real data like a spreadsheet. Open tables side by side in tabs, search and filter them, and fix a value in place. Changes wait until you press Apply, then all of them are saved or none are, so your live data is never left half-edited. Every row keeps a history of who changed what, and you can download any view as a CSV file. Removing someone from your list of users also removes their account, so only owners and admins can do it.
Transactional email
Email & pushEmail just works. Your app already sends sign-up codes, password resets and payment receipts, and any email your features need, like an order confirmation or a weekly summary, is added for you. There is no mail server to set up, and if your app speaks more than one language, each customer gets their emails in theirs. The Emails page shows what was sent and lets you put your brand on customer emails. If an address bounces, your app stops emailing it, marks that person on the Users page, and lets you send to them again once they fix it.
Related recipes
Post sign-ups and sales to Slack or Discord
Every new sign-up or sale shows up as a message in your team's Slack or Discord channel the moment it happens, so wins are seen and odd ones are caught early.
Live support chat
Visitors and users chat with you from a small bubble in your app, and you answer from a staff inbox that updates the moment a message arrives. If you're away, they leave an email and get the answer there.
Weekly metrics report
Every Monday morning, last week's sign-ups, active users, revenue and top items land in your inbox, with a copy kept so you can look back at the trend.