Automation

Two directions, one workflow builder.

A workflow can carry its own secret URL for your systems to post to, and any workflow can send an HTTP request out to an endpoint you control. That pair is how Spodus reaches a tool nobody has written a connector for.

Get a demo See all integrations

What Webhooks gives you.

Start a workflow from outside

Post JSON to a workflow's own URL and it runs. The body arrives as variables the steps after it can read, up to 64 KB.

Call your systems back

An HTTP request step sends GET, POST, PUT, PATCH or DELETE to an endpoint you control, with the record's own values written into the URL, the headers and the body.

A secret per workflow

The credential belongs to the one workflow it was minted for, is compared in constant time, and stops working the moment that workflow is switched off.

The specifics.

Every number on this page came out of the product rather than a roadmap.

Inbound: One URL per workflow, shown in the builder as its Live URL. POST JSON to it and the workflow starts. It answers only while that workflow is Active, so switching the workflow off closes the door.
How an inbound call is authenticated: By the secret in that workflow's Live URL, sent as an x-webhook-secret header or as a query parameter, and compared in constant time. It authorises that one workflow and nothing else.
What the workflow can read: The whole JSON body, up to 64 KB, addressed as variables in any step that follows. A body that is not JSON is refused rather than half-read.
Outbound: An HTTP request step in any workflow. You set the method, the headers and the body, and values from the record that triggered the run are written into all three.
Outbound timing: Five seconds, then the step fails. There is no retry, and a redirect counts as a failure. Private and loopback addresses are refused.
What else a workflow can do: Create, update, delete and search records, send email, branch on a condition, filter, and loop over what it found. An inbound call is not limited to one action.
What starts a workflow: An inbound call is one option among several. A schedule, a date arriving on a record, a form submission, a record changing, or somebody pressing Run all reach the same steps.
Plans: Growth and Business. Inbound and outbound are one entitlement, so a plan with either has both, and a workspace below it gets a 402 on the URL and a failed step in the run log.
Volume: Nothing is throttled per second. Every run counts against the plan's monthly automation allowance: 20,000 on Growth and 100,000 on Business.
Seeing what happened: The last 50 runs are kept, step by step, with each step marked as succeeded, skipped or failed.

Switching it on.

Build a workflow in Automations and choose the inbound webhook as its trigger. Only admins can author one.
Copy the Live URL, secret and all, and post your JSON to it.
To call outward instead, add an HTTP request step and point it at your endpoint.
Switch the workflow to Active. An inactive workflow's URL answers nothing.

This is not a general-purpose API.

There is no published set of endpoints, no schema document, no client library, and no credential you mint yourself and scope. Reading or writing records from your own code happens through a workflow or it does not happen. There is nothing to subscribe to either: Spodus calls your system when a workflow you built runs an HTTP step, not whenever a record changes. And the sharp edge worth knowing before you design around it: an outbound step does not capture what your endpoint replied, so a workflow cannot branch on the answer or write it to a record. It sends, it notes whether the call succeeded, and it moves on.

Questions, answered.

Can I read and write records from my own code?

Only through a workflow. There is no published set of endpoints, no schema document and no client library, and nothing in Spodus authenticates a credential you generate for yourself. What exists instead is one URL per workflow that your systems can post to, and a step that posts back out.

Which plans include this?

Growth and Business. The inbound URL and the outbound HTTP step are a single entitlement, so a plan with one has both. A workspace below Growth gets a 402 on the URL and a failed step in the run log.

Can Spodus push events to my system?

Only from inside a workflow. There is nothing to subscribe to and no list of endpoints to register: you add an HTTP request step and your URL is called when that workflow runs. So the useful question is what starts the workflow, which can be a schedule, a date on a record, an inbound call, a form submission or somebody pressing Run.

Can a workflow use my endpoint's response?

No. The step records whether the call succeeded and carries on, so nothing later can branch on the reply or save it to a record. If your integration depends on reading an answer back, have your own system post to the workflow's inbound URL instead and drive the next step from that.

The tool I want to connect is not listed here. Now what?

If it can call a URL, or be called at one, this is how you connect it, and most modern tools do both. If it cannot, the honest answer is that Spodus has no way to reach it today and there is no marketplace of connectors to go looking in.

The rest of the list.

It is a short one, and every page on it says exactly what its connection does and does not do.

Two directions, one workflow builder.

What Webhooks gives you.

Start a workflow from outside

Call your systems back

A secret per workflow

The specifics.

Switching it on.

This is not a general-purpose API.

Questions, answered.

The rest of the list.

CSV import

Gmail

Outlook

Bring your data. Keep your mailbox.

Two directions, one workflow builder.

What Webhooks gives you.

Start a workflow from outside

Call your systems back

A secret per workflow

The specifics.

Switching it on.

This is not a general-purpose API.

Questions, answered.

The rest of the list.

CSV import

Gmail

Outlook

Bring your data. Keep your mailbox.