Files
projectsend/.gitignore
T
ignacionelson 7059ee293a Add a Zapier guide to the API documentation page
The API has had everything Zapier needs since it shipped — a bearer
token, an auth-test endpoint at /me, and list endpoints that return
newest-first with a stable id, which is exactly the shape a polling
trigger wants. What was missing was anyone saying so.

This is written for somebody wiring up a Zap, not for somebody writing
code, which is why it is a second document rather than a section of the
guide. Same reason it renders in-app rather than linking to GitHub: the
installations most likely to need it are the ones least likely to have
outbound internet access.

It says out loud the two things that will otherwise be discovered the
hard way — a token expires within a year and nothing renews it, and a
deletion cannot start a Zap because polling cannot see one.
2026-08-25 01:08:09 -03:00

49 lines
1.1 KiB
Plaintext

.DS_Store
.env
.env.backup
.env.production
.phpactor.json
.phpunit.result.cache
/.fleet
/.idea
/.nova
/.phpunit.cache
/.vscode
/.zed
/bootstrap/ssr
/node_modules
/packages
/public/build
/public/hot
/public/storage
/storage/*.key
/storage/pail
/vendor
auth.json
Homestead.json
Homestead.yaml
npm-debug.log
yarn-error.log
/.release-build
/compose.override.yaml
/compose.override.yml
# ── Maintainer-only working files ──
# Planning notes, local tooling and development fixtures are kept outside
# this repository, so these paths are ignored here rather than published.
# If docs/ looks sparser than you expect, that is why. The two entries
# below the ignore are application data the app reads at runtime and are
# part of the repository.
/.claude
/scripts/refresh-sim.sh
/database/seeders/DevDataSeeder.php
/docs/*.md
!/docs/api-guide.md
!/docs/email-oauth.md
!/docs/api-zapier.md
# ── Local-only dev TLS ──
# mkcert certificates and the nginx config that terminates HTTPS on the
# dev `web` container. Machine-specific, and one of them is a private key.
/docker/web/local/