diff --git a/docs/04-activate/SETUP-ZAPIER-DEVELOPER.html b/docs/04-activate/SETUP-ZAPIER-DEVELOPER.html new file mode 100644 index 0000000..3be5621 --- /dev/null +++ b/docs/04-activate/SETUP-ZAPIER-DEVELOPER.html @@ -0,0 +1,235 @@ + + + + + + Set up a Zapier Developer account and push Verae Time + + + +
+
Verae Time · morning checklist
+

Set up a Zapier Developer account and push Verae Time

+

Create a developer account, push the private integration, and run Add Numbers (2 + 3 = 5). No Verae servers, no NATS, no public URL.

+
+
+

App path: packages/verae-activate in /Users/marchon/apps/zapier. Use zapier-platform to publish. Do not mix this with zapier-sdk.

+ +

0. What you will have when this works

+
    +
  1. A Zapier developer account (free).
    2. +
  2. A private integration named Verae Time.
    3. +
  3. A Zap: any trigger (e.g. Schedule) → Verae Time → Add Numbers.
    4. +
  4. A test that shows 2 + 3 = 5.
    5. +
+

After that, grow the same integration into timestamping.

+ +

1. Create the Zapier account (browser, ~5 minutes)

+
    +
  1. Open https://zapier.com/sign-up and create an account (Google/SSO is fine).
    2. +
  2. Confirm email if asked.
    3. +
  3. Open the Platform: https://developer.zapier.com. Same login. This is Zapier Platform, not the consumer app directory.
    4. +
  4. You should land on My Integrations (empty is fine).
    5. +
+

If you already have a Zapier account, skip sign-up and go straight to developer.zapier.com.

+ +

2. Install the CLI on this Mac (Terminal)

+

The CLI is already on this machine as zapier-platform (v19.1.0) in ~/.npm-global/bin.

+ 
export PATH="$HOME/.npm-global/bin:$PATH"
+zapier-platform --version
+

You want 19.x. If the command is missing:

+ 
npm install -g zapier-platform-cli
+export PATH="$HOME/.npm-global/bin:$PATH"
+zapier-platform --version
+

Do not use the old zapier binary if it is a different major from zapier-platform-core in the app (19.1.0).

+ +

3. Log the CLI into your account

+ 
zapier-platform login
+

A browser window opens. Approve the deploy key. This writes ~/.zapierrc (never commit that file).

+

SSO-only org:

+ 
zapier-platform login --sso
+

Check:

+ 
zapier-platform whoami
+ +

4. Register and push Verae Time

+ 
cd /Users/marchon/apps/zapier/packages/verae-activate
+npm install
+npm test
+zapier-platform validate
+zapier-platform register "Verae Time"
+zapier-platform push
+

register creates the integration and writes .zapierapprc (app id). Do commit .zapierapprc after register. Do not commit ~/.zapierrc.

+

push uploads a private version, visible only to your account until you invite others.

+

If register says the name is taken, use "Verae Time Dev" or "VeraeTime".

+ +

5. Enable the integration in the Zap editor

+
    +
  1. Open https://zapier.com/app/zaps → Create.
    2. +
  2. Trigger: Schedule by Zapier → Every hour (or any trigger that can fire a test).
    3. +
  3. Action: search Verae Time. If it does not appear: +
      +
    • In the Zap editor app search, open Change account / custom integrations.
      • +
    • Or visit developer.zapier.com → your app → Sharing.
      • +
    • Hard refresh. Private apps can take a minute after the first push.
      • +
    +
    4. +
  4. Connect Verae Time: +
      +
    • API Key — leave blank.
      • +
    • API base URL — leave blank.
      • +
    • Test connection → should succeed (Verae Time / local mode).
      • +
    +
    5. +
  5. Choose action Add Numbers, Echo Text, SHA256 Hash Text, or Create Timestamp (local mock if API fields blank).
    6. +
  6. Set Number 1 = 2, Number 2 = 3.
    7. +
  7. Test step. You want:
    8. +
+ 
{
+  "number1": 2,
+  "number2": 3,
+  "sum": 5,
+  "mode": "local"
+}
+

Turn the Zap on if you want it to keep running. Failures on Zapier are free; successes count as tasks.

+ +

6. Optional: point Add Numbers at your hosted zappier API

+

Only after packages/zappier is reachable on the public internet (ngrok, fly, etc.):

+
    +
  1. Sign up in packages/zappier portal (/portal) → copy API key.
    2. +
  2. In the Zapier connection, set API Key to that key and API base URL to https://<your-host> (no trailing path).
    3. +
  3. Re-test. mode becomes "hosted" and POST /v1/add is metered (list price free).
    4. +
+

Until then, leave both fields empty.

+ +

7. If something fails

+ + + + + + + + + + + + + +
SymptomFix
zapier-platform: command not foundexport PATH="$HOME/.npm-global/bin:$PATH"
Not logged inzapier-platform login
validate schema errorStay on zapier-platform-core@19.1.0 matching CLI 19.x
App not in Zap editorConfirm push on developer.zapier.com. Search “Verae”.
Connection test fails with blank keysOld push; pull and push again. Local test does not HTTP.
ENOTFOUND / timeoutYou filled API base URL. Clear it for Add Numbers.
Invite a teammatedeveloper.zapier.com → app → Sharing → invite email
+ +

8. What this is not

+ + +

9. Commands cheat sheet

+ 
export PATH="$HOME/.npm-global/bin:$PATH"
+cd /Users/marchon/apps/zapier/packages/verae-activate
+
+npm test
+zapier-platform whoami
+zapier-platform validate
+zapier-platform push          # after the first register
+zapier-platform versions
+zapier-platform logs
+

Official CLI docs: https://docs.zapier.com/platform/reference/cli-docs

+
+ + + diff --git a/docs/04-activate/SETUP-ZAPIER-DEVELOPER.pdf b/docs/04-activate/SETUP-ZAPIER-DEVELOPER.pdf new file mode 100644 index 0000000..92927f7 Binary files /dev/null and b/docs/04-activate/SETUP-ZAPIER-DEVELOPER.pdf differ