The general recipe for sending contributions from any tool that works with Zapier or Make.
If your tool works with Zapier or Make, it can send contributions to Equity Matrix. The tool guides in this section follow the recipe below.
The recipe
- Trigger: your tool’s “new record” event, like a new time entry, expense or invoice. Add “updated” and “deleted” events too, if your tool offers them.
- Filter to this company’s work. Most people track time for more than one company or client in the same tool. Add a filter step that only continues for the entries that belong to this Equity Matrix organization, by client, project, workspace or tag. Without it, every entry gets sent.
- Map the fields to a contribution:
- the person’s email →
memberEmail - hours or amount →
value - the record’s date →
date - the record’s notes →
description - the tool, record type and record ID →
externalId, likeharvest:time_entry:{id}
- the person’s email →
- Send it with an HTTP request to
POST https://api.equitymatrix.io/v1/contributions, with these headers:Authorization: Bearer em_live_your_key_hereContent-Type: application/json
- For deletes, send
DELETE https://api.equitymatrix.io/v1/contributions/external/{externalId}, and treat a404as done.
One organization per key
An API key sends contributions to one Equity Matrix organization. If you’re a member of more than one, create a key in each organization and build a separate Zap or scenario for each, with its own filter. For example, Harvest entries for client A go to one organization’s key, and entries for client B go to the other’s.
In Zapier
Use Webhooks by Zapier with the Custom Request action:
- Method:
POST(orDELETEfor deletes) - URL:
https://api.equitymatrix.io/v1/contributions - Data: the JSON body, with your mapped fields
- Headers:
Authorizationset toBearer em_live_your_key_here, andContent-Typeset toapplication/json
Webhooks by Zapier is a premium app, so it needs a paid Zapier plan.
In Make
Use the HTTP app’s Make a request module:
- URL:
https://api.equitymatrix.io/v1/contributions - Method:
POST(orDELETEfor deletes) - Headers:
Authorizationset toBearer em_live_your_key_here - Body type: Raw, with content type JSON, and your mapped fields in the body
Tips
- Use one API key per tool, named after it. Contributions then show
[via Harvest]or[via Toggl Track]in front of the description. - Always send an
externalId, so edits and retries update the same contribution instead of creating new ones. See Syncing with external IDs. - Match people by email. Each person’s email in your tool has to match their email in Equity Matrix. If it doesn’t, add a lookup table step that maps your tool’s users to their Equity Matrix email.
- In Zapier, add a Filter by Zapier step after the trigger. In Make, set a filter on the link between the trigger and the HTTP module.
- Check the API Keys page if contributions stop showing up. Each key shows its most recent error.