IntegrationsAlbato
Send replies to your apps on Albato, and leads back into GetSales.
Connect GetSales in Albato with an API key and pick a trigger. A reply, a hand-off or a website visit starts the automation, and GetSales actions add people to a table or a workflow from any app Albato connects.
- ConnectSettings, API keys
- DirectionBoth ways
- Credits0 per event
What moves between GetSales and Albato: an event such as a reply, a hand-off or a website visit starts an automation, and Albato's actions add a person to a table, add people to a workflow or find a person in GetSales.
A reply, a hand-off, a visit to A trigger starts the automation
GetSales to Albato, as an event
A person in a table to Add a person to a table
Albato to GetSales, skipped if GetSales has them
People in a workflow to Add people to a workflow
Albato to GetSales, the workflow's steps take over
A person found to Find a person
Albato reads it from GetSales
What it does
What starts an automation,
and what Albato can do
One trigger for any GetSales event, named triggers for the common ones, and four actions.
Triggers: GetSales to Albato
- Watch events
Pick the GetSales events you want in one trigger. Albato subscribes and unsubscribes for you.
- Reply received
A lead answered on LinkedIn or by email.
- Task created
A task for someone on your team, the AI SDR's hand-offs included.
- Five more
Conversation state changed, Lead finished or left a workflow, Website visit identified, Import or search finished, Sender profile health changed.
Actions: Albato to GetSales
- Add a person to a table
From a form, a CRM or a sheet. A person GetSales already has is skipped, not changed.
- Add people to a workflow
Pick the workflow and they enter its steps. Your stoplist still holds.
- Find a person
Look a person up in your tables and use their fields in the next steps.
- Any API call
Any call of the GetSales API the key's permissions allow, with the same connection.
Not in this version
- Sending messages
Albato cannot send a LinkedIn message or an email. Add people to a workflow and its steps send.
- Building workflows or tables
Albato cannot create or edit a workflow, a table or a column. Build them in GetSales.
- Connection accepted
No trigger fires when someone accepts a connection request.
- Updating people
Albato cannot change the fields of a person already in GetSales.
When it runs
Start it once,
it keeps running
GetSales runs in an Albato automation like any other app.
On an event
The trigger fires when GetSales records the event: a reply lands in Unibox, a task opens, a person leaves a workflow.
After any app
The actions run after any app Albato connects, such as a form, a CRM or a spreadsheet.
Then in GetSales
A person added to a table meets its Auto-run columns, and people added to a workflow start its steps. Nobody has to press run.
What it costs
Nothing
per event
Events, reads and writes move your own data, so GetSales charges no credits for them. What an action starts in GetSales is billed as it is in the app.
What a credit costs- An event sent to Albato
- 0
- A person added, found or added to a workflow
- 0
- A column that runs on the new row
- Its own rate
- AI steps and the AI SDR's work in the workflow
- As in the app
Set it up
Connected
in five steps
Create a key
In GetSales, open Settings, API keys and click Create key. Pick the Automation platform preset, name it Albato and copy the secret: it is shown once.
Connect Albato
In Albato, create an automation, choose GetSales and paste the key to connect.
Pick a trigger
Choose Watch events or a named trigger such as Reply received. Albato subscribes for you.
Map the fields
Add the next app, or a GetSales action, and map the fields from the trigger.
Start it
Test the automation once, then start it.
You need a GetSales user who can manage API keys. A key works for one workspace.
How does the Albato integration work?
Create an API key in GetSales and connect GetSales in Albato with it. A GetSales trigger starts an automation on the events you pick, and the GetSales actions add a person to a table, add people to a workflow, find a person or make any API call.
Which triggers are there?
Watch events takes any event GetSales sends to webhooks, picked from a list. The named triggers cover the common ones: Reply received, Task created (it carries the AI SDR's hand-offs), Conversation state changed, Lead finished or left a workflow, Website visit identified, Import or search finished and Sender profile health changed.
Can Albato add people to a GetSales workflow?
Yes. Add a person to a table or find one, then use Add people to a workflow with the workflow picked. They enter its steps as people added by hand do, and a person on your stoplist does not enter.
Is there an action for any API call?
Yes. Besides the three named actions, one action makes any call of the GetSales API the key's permissions allow, for what the named ones do not cover.
Can I send LinkedIn messages or emails from Albato?
Not in this version. Sending stays in GetSales: add the person to a workflow and its steps send from your sender profiles, paced within each account's limits.
What happens when a person is already in GetSales?
Add a person to a table skips them and returns the person GetSales has, so the next step can still add them to a workflow. Their fields are not changed: updating people is not in this version.
Does the Albato integration cost credits?
Events, reads and writes cost no credits. What an action starts is billed as it is in the app: a column with Auto-run on the new row at its own rate, and the AI work of a workflow step or the AI SDR. Albato counts its own usage on your Albato plan. What a credit costs is on the pricing page.
Your apps, connected
Every reply, in the apps you already use.
Connect GetSales in Albato once. Replies reach your other apps, and Albato keeps your tables and workflows filled.
- People added to the table7Done
- Already in GetSales3Skipped
- Added to the follow-up workflow10Done
0 credits for the writes. The workflow's steps start for all ten.
Replies in GetSales. Your apps on Albato.
