The first
deploy registers the function through telnyx-edge new-func. Every deploy generates .telnyx/ inside the project, which The Generated Code opens, links @telnyx/acp and @telnyx/edge-runtime into .telnyx/node_modules from the CLI’s own copies, bundles the entry’s module graph on this machine and ships one file. The platform builds it, typically about ten minutes the first time (deploy waits up to 25), and every deploy after that is a new revision, listed by versions. What it set up, the function, the mount URL, the actor type, the artifacts and the revision, is recorded under deployed in agent.json, which every later verb reads.
Around the function it sets up what agent.json declares. Each phone number is put on a Call Control application and a messaging profile, created when the number is bare. An email inbox is found or created and its domain subscribed to email.received. Each artifact’s webhook is pointed at the function, with the previous webhook remembered so that remove and delete can restore it. It ends by printing the channels, the address, and the page URL and embed tag when web is set. A number’s line ends with what its texting cannot do when the number’s features say so, domestic texts only: … for one that can neither receive nor send international SMS. A messaging profile deploy creates is open to every destination.
A project with a phone number, an email inbox or a channel needs the TELNYX_PUBLIC_KEY secret, and deploy asks for it once on a terminal; in a script it stops and names the secret, so add secret TELNYX_PUBLIC_KEY first. Deploy and Operate walks through a deploy and what to do when one fails.