Docs
Reference

Appwrite

Push a penv environment into an Appwrite function's variables as secrets.

Push a penv environment into an Appwrite function's variables as secrets.

The connection

WhatThis provider
VendorAppwrite
Keyappwrite-function-variable
Availabilityavailable. You can connect it today.
Credential penv holdsappwrite-key
Values read backno
Activationon-next-deploy

What it moves

DirectionWhat it does
exportWrites names and values from penv into the store.

Appwrite returns no value once it holds one, so penv can write here and cannot read back.

When a written value goes live

on-next-deploy. A new value waits there and arrives with your next deploy.

What happens to a name that exists

DirectionPolicies you can pick
exportcreate_only, overwrite, overwrite_and_prune

How syncs work says what each one does.

How you connect

You paste a credential you already hold. penv seals it and never shows it again.

FieldLabelKindRequiredWhat it is
apiKeyAPI keysecret, masked here and sealedyesA server API key with functions.read and functions.write.

What the connection asks for

Fixed when you connect, and shared by every mapping on it.

FieldLabelKindRequiredAdvancedWhat it is
projectIdProjecttextyesnoThe project ID from your Appwrite console.
regionRegiontextnoyesLeave empty unless your project's API endpoint shows a region.

What a mapping asks for

Answered once per environment you map.

FieldLabelKindRequiredAdvancedWhat it is
functionIdFunctiontextyesnoThe function whose variables this environment maps onto.

Permissions it needs

penv probes for these when it verifies the connection.

PermissionDirectionsBlockingWithout it
functions.readevery directionyesPreview cannot list the function's variables.
functions.writeexportyesExport cannot write anything.