Integrations

Make

Make receives UpVoiced events through a custom webhook. A filter right after it recomputes the signature with Make’s own sha256 function, so later modules only see deliveries UpVoiced really sent.

Receive events

1. In a new scenario, add Webhooks › Custom webhook and click Add. Under Advanced settings, set Get request headers to Yes and JSON pass-through to Yes: the signature covers the raw body, so the scenario needs the JSON as text, exactly as sent, plus the headers. Copy the webhook address.
2. In UpVoiced, add a webhook endpoint with that address (owners and admins: Settings → Integrations → Webhooks, or POST /v1/webhooks) for the events this scenario handles. Copy the signing secret (whsec_…): it is shown once.
3. Click Run once in Make, then make UpVoiced send something: Send test on the endpoint (or POST /v1/webhooks/{id}/test), or create a test post. Make learns the data structure from that request.
4. Add Tools › Set variables after the webhook (module 2 below) with two variables, mapping from the webhook (module 1):
   • signature: {{get(map(1.headers; "value"; "name"; "x-upvoiced-signature"); 1)}}
   • timestamp: {{replace(first(split(get(map(1.headers; "value"; "name"; "x-upvoiced-signature"); 1); ",")); "t="; "")}}
   Request headers arrive as a list of name and value items; map picks the value named x-upvoiced-signature, and the timestamp is its first part after t=.
5. Add JSON › Parse JSON (module 3) with the webhook’s body text as the JSON string, then the modules you want.
6. Click the link between modules 2 and 3 and add a filter named “Signed by UpVoiced” with the two conditions below (both must pass). Then turn the scenario on.

The signature filter

Fill the three arguments of sha256(text; encoding; key):

With a key, Make’s sha256 returns the HMAC-SHA256 that UpVoiced puts after v1=. During a secret rotation the header carries one v1= per valid secret, so contains (not equals) is the right operator. Bundles that fail the filter stop there; Make has already answered UpVoiced with 200 Accepted, so they are not retried.

Check your formula

Before real deliveries arrive, evaluate your sha256 function once with these fictional values (for example in a temporary Set variables module). It must return the expected value exactly.

Recipes

After Parse JSON, map type, id (the event id, the same on every redelivery: use it as the unique key of what you create) and the fields under data. To handle several events in one scenario, add a Router with a filter on type per route.

Create posts from a scenario

Any module’s output (a form answer, a CRM record, a help-desk conversation) can become a post through POST /v1/posts. Add HTTP › Make a request:

• Authentication type: API key. Create a keychain with Key Bearer uv_live_… (an API key with the write scope), API key placement in the header and API key parameter name Authorization.
• URL https://api.upvoiced.com/v1/posts, Method POST.
• Headers: X-Workspace = your workspace id, and Idempotency-Key = a value built from the source record’s id (8 to 128 characters from [A-Za-z0-9_.:-]), so a re-run creates one post.
• Body content type application/JSON with the Data structure input method, which escapes quotes and line breaks in mapped values for you. Fields below.
• Parse response: Yes, to map the created post’s id later.