Design notes on the CSV export

Our ops team has a runbook step purely to work around it. It would pay for itself in the first month.

How it works

The workaround breaks as soon as a second person is involved. Our ops team has a runbook step purely to work around it. Not urgent, but it would save everyone about an hour a week.

Step by step

We would move our whole team over if this landed. Even shipping it behind a flag would let us validate the approach. Our ops team has a runbook step purely to work around it.

1. Enable custom domains.
2. Enable CSV export.
3. Enable post templates.

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

Common pitfalls

Screenshots are attached in the thread below. It was the first thing our new hires tripped over. Our response times would improve without adding headcount.

Next steps

We hit this every Monday during the weekly review. We would stop exporting to a spreadsheet every Friday. We have a Zapier hack doing this today and it breaks weekly.

Step by step

Our support volume would drop noticeably if this shipped. We would move our whole team over if this landed. Customers ask about this on nearly every onboarding call.

1. Enable a public API rate-limit dashboard.
2. Enable reaction emoji.
3. Enable a Linear two-way sync.
4. Enable SAML SSO.