Skip to main content

Using Florbs webhooks for process automation

Integrate your external systems with Florbs using Webhooks as workflow triggers

Tanya Babina avatar
Written by Tanya Babina
Updated over 2 weeks ago

Want to connect Florbs with your existing tools or a custom-built solution? Webhooks make it simple to integrate your processes and kick off workflows automatically.

Create a Webhook in just a few clicks

Set up your webhook and you’re ready to go.

  1. Click on + Add webhook

2. Click "Confirm".

Use the webhook as a trigger inside a Florbs workflow

Once created, your webhook can be used as a trigger inside any Florbs workflow.

Test with webhook playground

You can also test your setup using the webhook playground, which includes a ready-made example for quick reference.

FAQ

Q: What format of data should I send to the webhook?

A: JSON with key-value pairs such as:

{

"USER": "john@example.com",

"SHARED_MAILBOX": "shared@example.com"

}

Note: The example above is pretty-printed. For calculating the signature the payload must not contain any whitespace characters.

Q: How can I access the data passed to the webhook in the workflow?

A: Florbs uses Mustache syntax to read fields from the webhook payload (e.g. {{USER}} or {{SHARED_MAILBOX}}). You can use these placeholders in any workflow configuration field as in the image below.

Q: How do I calculate the request signature?

A: Florbs validates each request using an HMAC-SHA256 signature.

  • Use your UTF-8 encoded Secret Key as the HMAC key.

  • Build the message by concatenating: timestamp + "." + payload

  • Make sure the payload contains no whitespace.

You can find a complete sample in the Playground.

Q: Why am I getting “Request timestamp is too old”?

A: Florbs accepts webhook requests within 15 minutes of the timestamp.

If the timestamp is older, the request is rejected for security reasons.

Q: Why am I getting an “Invalid signature”?

A: The signature doesn’t match what Florbs expects. A common cause is including whitespace in the payload used for signature calculation. Ensure your payload is compact (no spaces, tabs, or newlines), and see the Playground example for guidance.

Did this answer your question?