Digital Foundations
Set Up ClickSend and Get Your API Credentials
The small piece of plumbing behind an automated text message.
If you want review requests, reminders or confirmations to leave your business as text messages, you need a messaging account and two pieces of information. Here’s how to get them, where to find them, and how to keep them out of trouble.
What you’re actually setting up.
A text message doesn’t come out of Airtable. Something has to physically deliver it to a customer’s phone. A messaging provider sits in the middle: your automation makes a request, the provider sends the message, you pay for what you send.
- Job completeSomething real happened in the business
- Your automation runsAirtable, Make, Zapier or a script
- ClickSend receives the requestIt checks who you are
- Customer receives a textA short message with one link
- Customer decidesThey open the link or ignore it
You don’t have to use ClickSend.
It’s a common example because it’s easy to set up and works with most automation tools. The same setup applies to any messaging provider: create an account, find your credentials, put them into your automation, test one message. Only the menus change.
Two questions before you sign up.
A messaging account is easy to create and easy to forget about. A quick check first saves you from paying for something you didn’t need.
- Have you already proven that customers respond to an email request?
- Do you actually have mobile numbers for the customers you want to contact?
- Are you happy paying a small amount for every message you send?
- Do you know what the message says before you connect anything?
A text is a paid message
If email requests aren’t working yet, fix the message before you spend money delivering it.
Create the account.
Sign-up takes a few minutes. Use details that belong to the business, not to one person’s personal inbox.
- 01
Open the ClickSend sign-up page
dashboard.clicksend.com/signup
- 02
Enter your name, business details, business email and a password
- 03
Check your email and verify the address
The message can take a couple of minutes to arrive
- 04
Log in to your new dashboard
- 05
Add credit when you’re ready
New accounts are often given a small trial credit — check what’s currently offered
Use an address you control
Don’t register with a personal email or a login belonging to a former employee. If someone else controls the inbox, they can reset the password and take the account with them.
Find your API credentials.
This is the bit everyone hunts around for. You’re after two values: your username and your API key.
- 01
Log in to your ClickSend dashboard
- 02
Look in the top-right corner for the key icon or API Credentials
On some accounts it sits under Profile or Developers
- 03
Copy your Username
It may already be filled in for you
- 04
Copy your API Key
Use the copy button rather than selecting the text by hand
- 05
Paste both into your automation or password manager
| Credential | What it is | Treat it like |
|---|---|---|
| Username | Identifies which account the request belongs to | A username — low risk, but don’t advertise it |
| API Key | Proves the request is really from you | A password. Because it is one. |
The menus move
Providers redesign their dashboards constantly. If the option isn’t where this guide says, search inside the dashboard for “API”, or check ClickSend’s current help centre. The credentials themselves work the same way.
What those two values actually do.
Every request your automation makes has to prove who it’s from. ClickSend uses your username and API key together, the same way a website uses a username and password.
When
Your automation runs
It sends
The message, the number, your username and your API key
ClickSend checks
Do these two match a real account with credit?
Then
The message is delivered and your balance is reduced
One quirk worth knowing: many tools label this field Password. In that box you put your API key, not the password you use to log in. It’s the most common reason a first test message fails.
You don’t need to understand the plumbing
If you’re using Airtable, Make or Zapier, the tool handles the request for you. You just supply the two values.
Keep them somewhere sensible.
An API key can send messages using your credit and read the account details attached to it. That means it deserves the same care as your banking passwords — and it gets forgotten far more often.
- Store it in a password manager, not a note on your desktop
- Don’t paste it into emails, chats or screenshots
- Don’t commit it to code or a public repository
- Don’t share it with anyone who doesn’t need it
- Keep a note of where it’s being used, so you can update it later
- If it leaks, regenerate the key and update your automation
Credential record card
Provider: ClickSend Account email: Username: (your ClickSend username) API key: kept in the password manager — not written here Dashboard: https://dashboard.clicksend.com Used by: (Airtable automation / Make / Zapier) Added: (date) Checked: (date)
Copy this into your password manager and fill it in. It records the boring-but-useful details without keeping the actual key in a text file.
Put them into your automation.
Every tool labels these fields slightly differently. The values behind them are the same.
| Field you might see | What to put in it |
|---|---|
| Username / User / Account | Your ClickSend username |
| API Key / Secret / Token | Your API key |
| Password | Your API key (not your login password) |
| From / Sender ID | A registered sender ID, or leave the default |
| To / Recipient | Mobile number including the country code, e.g. +61 4xx xxx xxx |
| Message / Body / Content | Your message text |
Save, then stop
Finish this step and don’t turn the automation on until you’ve tested it in the next one.
Test it with one message to yourself.
Before this touches a customer, send a single message to your own mobile. It proves the credentials work, the number format is right and you know what the message looks like on a real phone.
- Add enough credit to send a message
- Send one message to your own mobile number
- Check that it arrives
- Check the sender name the customer would see
- Check how much it cost
- Check whether it arrived as one message or two
- Read it on your phone and decide whether you’d be happy receiving it
Test message
Hi [Name], this is a test message from [Business Name]. If you can read this, our review request system is working. Thanks, [Name]
One message, one number
Don’t run this against your whole customer list until it has worked from beginning to end.
Know what you’re paying for.
Messaging providers usually work on pay-as-you-go credit rather than a monthly plan. A few things quietly change the cost.
- Long messages split into multiple parts, and each part is charged
- Some countries and networks cost more than others
- A custom Sender ID may need to be registered before you can use it
- Unused credit may not be refundable or transferable
- Marketing texts have strict permission rules in Australia — get consent first and make opting out easy
Check the current details
Pricing, free trial credit, sender ID rules and dashboard layout all change. Look at ClickSend’s current pricing and help pages while you set this up rather than relying on an old screenshot or an old guide — including this one.
When the first message fails.
“Username or API key are incorrect”
Usually a login password in the API key box, a key copied with a space at the end, or a key that was regenerated after you set things up.
Nothing arrives
Check the automation actually fired. Then check the number format — include the country code rather than a local 04xx number.
Insufficient credit
The account is real and the credentials are fine. Top up and send the test again.
Sender ID not recognised
Some networks need your sender name registered or approved before messages go out. Ask the provider’s support what that account needs.
Work through these one at a time. Almost every first attempt failure is one of the four.
This is still an asset you own.
You created the account. It sits behind an email address you control. Your customer records live in your own table. The messaging provider is doing one job — delivering text — and it is a job you could move somewhere else.
Account you created
Signed up with business details
Email you control
You can reset the password yourself
Data in your table
Not locked inside someone else’s platform
If you ever change providers, your workflow doesn’t change. You swap two values in one box and update the name of the tool. That’s the difference between owning a system and renting a black box.
You’ve got the plumbing. Now build the process.
Guide
Build a Simple Review Request System
The workflow these credentials plug into — turn a finished job into a review request without remembering to send it.
Available now
Guide
Build Your Customer Database for Free
The customer list that makes any of this worthwhile — one simple table you own and can use again.
Available now
Got stuck?
Have a crack first.
If you’ve followed the guide and something isn’t working, tell us where you’ve got to and we’ll point you in the right direction.
Build assets. Not dependencies.
Own the account. Own the credentials. Own the data.
A messaging provider is a utility, not a partner.
Set it up yourself, keep the keys somewhere safe, and understand how it fits together.
Then you can change any piece of it without starting over.