How Soylent cut triage time in half

This blocks the quarterly report we send to the exec team. It is the single biggest reason our team still keeps a second tool open. Screenshots are attached in the thread below.

What changes

Happy to test a beta build if that helps. The workaround breaks as soon as a second person is involved. Two people on the team have independently asked for this.

1. Enable Zapier triggers.
2. Enable bulk actions.
3. Enable scheduled digests.
4. Enable granular email preferences.

Step by step

This blocks the quarterly report we send to the exec team. Happy to test a beta build if that helps.

curl -sS https://api.example.test/v2/items \
  -H "Authorization: Bearer $BULLETIN_API_KEY"

Next steps

Customers ask about this on nearly every onboarding call. Our ops team has a runbook step purely to work around it.

1. Enable reaction emoji.
2. Enable granular email preferences.
3. Enable webhook retries.
4. Enable custom domains.

Common pitfalls

We have a Zapier hack doing this today and it breaks weekly. We are working around it with a spreadsheet, which is not sustainable. It would let us retire an internal tool nobody wants to maintain.

1. Enable a public API rate-limit dashboard.
2. Enable SAML SSO.
3. Enable CSV export.

What changes

Even a read-only version would unblock us. We hit this every Monday during the weekly review. It would remove the last manual step before we can automate this.