Fyno’s Quick-Start Guide
Fyno is an all-in-one Customer Communications Management (CCM) platform. Connect your providers once, manage every template in one place, and send across SMS, WhatsApp, Email, Push and more through a single API, with unified analytics for every channel and provider.
This guide takes you from a fresh account to your first delivered notification in five steps. Each step includes a short video so you can follow along on screen.
- Time needed: about 15 minutes.
- You’ll need: a Fyno account and credentials for at least one communication provider (for example, an SMS or email provider).
At a glance
Configure your integrations
Connect the channels and providers you already use. No custom API integration work is needed on your side.
- Log in to your existing provider’s dashboard and copy its authentication credentials (API keys, tokens, sender IDs and so on).
- In Fyno, open Integrations, select your provider, and paste in the credentials to activate it.
Fyno supports 80+ providers across SMS, RCS, WhatsApp, Email, Push, Web Push, In-App, Voice, and Chat (Slack, Discord, Teams). Using a provider that isn’t listed? Let us know and we’ll help you get it added.
→ Learn more in the Integrations documentation.
Create your templates
Templates hold all your message content, organised by channel, so your code never has to.
- Edit visually. Use the WYSIWYG (“What You See Is What You Get”) editor to create and edit templates on the fly.
- Make it dynamic. Add Handlebars-style
{{ }}placeholders for values you pass at send time. - One template, many channels. Rich formatting is available on channels like Email and WhatsApp; SMS content is plain text.
- Test before you ship. Click Run Test to check the template renders as expected.
Already have templates elsewhere? Share them with us and we can pre-load them into your account.
→ Learn more in Templates and Handlebars.
Generate an API key
Every API call to Fyno is authenticated with an API key tied to your workspace.
- Click Workspace Settings in the bottom-left corner of the navigation menu, then click API Keys.
- Click Generate +.
- Enter a unique name for the key so you can tell your keys apart later.
- (Optional) Enter the IP addresses you want to restrict this key’s usage to.
- Select the environment the key should work in (see the table below).
- Click the check mark, then click Create.
- Before closing the pop-up, copy both your Workspace ID and your API key.
Save your key right away. Once the pop-up is closed, the API key can’t be retrieved again, and you’ll need to generate a new one.
You can create up to 20 API keys per account. → Learn more in API Keys.
Create a notification event
A notification event ties everything together into a single endpoint your application calls to send a message.
Notification Event = Template + (Providers or Route)
- Go to Notification Events in the left navigation and click Create +.
- Enter a name, choose the event type (OTP, Transactional, or Marketing), add a description, and select a group. Optionally, choose a subscription topic. Click Submit.
- Under Template, select the template you created earlier.
- Under Route/Provider, choose Single Channel Route or Provider, then pick a provider or route for each channel in your template.
- Click Save to save a Test version, or Go Live to publish the Live version.
- Click Run Test, enter a destination and placeholder values, and fire a test notification.
Trigger the event using the Fyno API
Once it works, trigger the event from your application with one API call, using the API key and Workspace ID from the previous step.
Change without redeploying. Saving a Test version never affects the Live version in your application. And because your code only references the event name, you can swap templates, channels, or providers on Fyno anytime without touching code.
→ Learn more in Creating a Notification Event and Triggering a Notification Event.
Monitor with analytics and logs
Your notifications are now flowing to customers. Use analytics and logs to measure performance and troubleshoot in seconds.
For delivery and open rates on a single event, see Notification Event Analytics. To inspect individual messages, see Sent Logs.
You’re all set 🎉
You can now send notifications across every channel through a single API. Here’s where to go next: