Nº 36 · Integrations
Build on SIGNL with REST API Credentials
Saved API keys for reaching an app with no connector. See what syncs, where it stops and how to set it up.
Applications open soon
See the whole workspaceWorks with REST API Credentials
What it does
Saved API keys the HTTP Request action reuses, each bound to the hosts it may be sent to. This is how you reach an app SIGNL has no dedicated connector for.
What syncs
What it covers
4- Bearer / header / basic / query auth
- Host allow-list per credential
- Rotate in one place
- Secret never returned to the browser
Automation actions
2- Fire Webhook
- HTTP Request
What it does not do
- A credential is sent only to the hosts listed on it. A credential with no hosts is refused.
Set it up
Connect in SIGNL
- Add a credential with the hosts it may be sent to. A credential with no hosts is refused.
- Pick it in an automation's HTTP step.
Questions people ask
What does SIGNL send to REST API Credentials?
To REST API Credentials: Bearer / header / basic / query auth, Host allow-list per credential, Rotate in one place, Secret never returned to the browser. Data moves one way, out of SIGNL.
How do I set up the connection to REST API Credentials?
It takes 2 steps, listed above. The first: Add a credential with the hosts it may be sent to. A credential with no hosts is refused.
Where does the connection to REST API Credentials stop?
Here is where the REST API Credentials connection stops. A credential is sent only to the hosts listed on it. A credential with no hosts is refused.
How ready is the connection to REST API Credentials?
The REST API Credentials connection is built and switched on for every workspace.
Can an automation start from or act on REST API Credentials?
Yes. The builder offers 2 actions (Fire Webhook, HTTP Request).
Keep going
All product names and logos belong to their owners. They identify integrations only and do not imply endorsement.