Make scenarios for e-signatures: what you can build with Salsox now

Why there is no module yet

A Make module talks to an app through its API: it asks for data, sends commands, and receives instant triggers through webhooks. Salsox has neither a public API nor webhooks today, so there is nothing for a module to call. The module is planned on top of both. Until then, the dependable signal Salsox produces is email, and Make is good at email.

Option one: a mailhook

Make can give you an email address of its own, called a mailhook, that starts a scenario whenever a message lands there.

1. Create a scenario and add Mailhook as the first module. Make shows an address ending in @hook.eu1.make.com or similar.
2. In your own mailbox, add a rule that forwards messages whose subject contains is signed by everyone to that address. Restrict the rule to the address Salsox sends from.
3. Finish a test document so a real message reaches the hook, then click Run once to capture its structure.
4. Use a Text parser module with a pattern match to take the document title from between the quotation marks in the subject, and the download link from the body.
5. Route the result where it is needed: an Airtable record, a Google Sheets row, a Trello card moved to "Signed", a Slack or Teams message.

Because the mailhook fires the instant the forwarded email arrives, this is the closest thing to a real-time trigger available today.

Option two: the Gmail module

If you would rather not set up forwarding, start the scenario with Gmail > Watch emails, filtered on the same subject text and sender. The scenario runs on Make's schedule, every fifteen minutes on most plans, so expect a short delay. Everything after the trigger is the same as above.

Routing by outcome

Add a Router after the trigger and you can handle different messages in one scenario: completion goes to your records, declined to sign goes to the person who owns the deal, Signing links for "Title" expired creates a follow-up task. Each path filters on the subject line.

Limits to plan around

Email-based scenarios see what the email says and nothing more. They cannot start a signing request, they do not know the individual signers, and a change to an email's wording would break the parser, so keep your patterns loose. Treat them as a bridge, not a foundation.

What a module will change

The planned module brings instant triggers per signature and per document, actions to send a template to new recipients, and the signed PDF as a file. If your scenario needs something specific, describe it on the contact page; requests shape what is built first.