Workspaces
Zapier and Make
On the web
Connect Zapier or Make once and every new lead from your bio page lands in a Google Sheet, Slack, HubSpot, Mailchimp or a text to your phone, within a minute, without anybody copying it across. Sales, comments, applicants, posts and approvals can go the same way.
Settings: Automations
Not captured yet
This picture is taken from the running app, not drawn by hand. Run npm run docs:shots to take it.
settings-automations.png
Connect Zapier
- 1Make a Zap with a webhook triggerIn Zapier, pick Webhooks by Zapier as the trigger, then Catch Hook, and copy the URL it shows you.
- 2Paste it into MORRSettings, then Workspace, then Automations, then Connect Zapier. Or open Send leads to Zapier or Make under your leads.
- 3Pick what to send and saveNew lead is ticked already. MORR sends a sample of each event you picked the moment you save.
- 4Test the trigger in ZapierPress Test trigger. The sample is there with every field, ready to map into the next step.
Connect Make
- 1Add a custom webhookIn a Make scenario, add Webhooks, then Custom webhook, press Add, and copy the address.
- 2Leave Make listeningIt says Determining data structure. Paste the address into MORR's Connect Make and save.
- 3Make learns the fieldsThe sample MORR sends on save teaches Make every field. Carry on building the scenario from there.
What can be sent
| Event | When | Carries |
|---|---|---|
| New lead | A contact or booking form on your bio page is filled in | Name, email, message, the block, where they came from, and the page |
| New subscriber | Somebody joins your list from your bio page | Name, email, where they came from, and the page |
| New sale | A product sells from your bio page | Product, amount and currency, buyer name and email |
| Post went out | A scheduled post publishes | Platform, type, caption, the media, when it went, and the link to it |
| Post failed | A scheduled post could not publish | The same, with the reason |
| New comment | A comment lands in your Inbox | Who wrote it, what they said, and the post it is on |
| New applicant | A creator applies to one of your programs | The pitch, their answers, their channels, and the program |
| Approval decided | A pipeline card is approved or sent back | The card, the decision, and its status |
Every delivery is JSON with the same outside: event, id, occurred_at, workspace (its id and name) and data, which holds the fields above. A sample carries "test": true, so a Zap can ignore it with a filter once it is built.
When it goes wrong
| The connection says | What it means |
|---|---|
| Last delivered 4 min ago | Working. Details shows the last few deliveries and what each got back. |
| Failing since… | The address answered with an error or did not answer. MORR tries again after 1, 5, 30 and 120 minutes, then gives up on that one delivery. |
| Paused after three days of failing | Every delivery failed for three days, so MORR stopped. Fix the Zap or scenario (usually it was turned off or deleted), then switch the connection back on. |
| Paused | Somebody switched it off. Nothing is sent, and nothing is saved up for later. |
| Who | Can |
|---|---|
| Owners, admins and members | Connect, change, pause, send samples and delete, and see the signing secret. |
| Everyone else in the workspace | See what is connected and whether it is working. |