Automate Twilio Serverless
HumDay reads Twilio Serverless’s own published API description and derives 39 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Twilio Serverless is
This is the public Twilio REST API.
API host: serverless.twilio.com
What HumDay can do in Twilio Serverless
17 documented operations change something in Twilio Serverless.
- POSTCreate a new Service resource.
/v1/Services - POSTCreate a new Asset resource.
/v1/Services/{ServiceSid}/Assets - POSTCreate a new Build resource.
/v1/Services/{ServiceSid}/Builds - POSTCreate a new Function resource.
/v1/Services/{ServiceSid}/Functions - POSTCreate a new environment.
/v1/Services/{ServiceSid}/Environments - DELETEDelete a Service resource.
/v1/Services/{Sid} - POSTUpdate a specific Service resource.
/v1/Services/{Sid} - POSTCreate a new Variable.
/v1/Services/{ServiceSid}/Environments/{EnvironmentSid}/Variables - POSTCreate a new Deployment.
/v1/Services/{ServiceSid}/Environments/{EnvironmentSid}/Deployments - DELETEDelete an Asset resource.
/v1/Services/{ServiceSid}/Assets/{Sid} - POSTUpdate a specific Asset resource.
/v1/Services/{ServiceSid}/Assets/{Sid} - DELETEDelete a Build resource.
/v1/Services/{ServiceSid}/Builds/{Sid} - DELETEDelete a Function resource.
/v1/Services/{ServiceSid}/Functions/{Sid} - POSTUpdate a specific Function resource.
/v1/Services/{ServiceSid}/Functions/{Sid} - DELETEDelete a specific environment.
/v1/Services/{ServiceSid}/Environments/{Sid} - DELETEDelete a specific Variable.
/v1/Services/{ServiceSid}/Environments/{EnvironmentSid}/Variables/{Sid} - POSTUpdate a specific Variable.
/v1/Services/{ServiceSid}/Environments/{EnvironmentSid}/Variables/{Sid}
What HumDay can read from Twilio Serverless
These are the operations a schedule or a trigger can watch.
- GETRetrieve a list of all Services.
/v1/Services - GETRetrieve a list of all Assets.
/v1/Services/{ServiceSid}/Assets - GETRetrieve a list of all Builds.
/v1/Services/{ServiceSid}/Builds - GETRetrieve a list of all Functions.
/v1/Services/{ServiceSid}/Functions - GETRetrieve a list of all environments.
/v1/Services/{ServiceSid}/Environments - GETRetrieve a specific Service resource.
/v1/Services/{Sid} - GETRetrieve a list of all Asset Versions.
/v1/Services/{ServiceSid}/Assets/{AssetSid}/Versions - GETRetrieve a list of all Function Version resources.
/v1/Services/{ServiceSid}/Functions/{FunctionSid}/Versions - GETRetrieve a list of all logs.
/v1/Services/{ServiceSid}/Environments/{EnvironmentSid}/Logs - GETRetrieve a list of all Variables.
/v1/Services/{ServiceSid}/Environments/{EnvironmentSid}/Variables - GETRetrieve a list of all Deployments.
/v1/Services/{ServiceSid}/Environments/{EnvironmentSid}/Deployments - GETRetrieve a specific Asset resource.
/v1/Services/{ServiceSid}/Assets/{Sid} - GETRetrieve a specific Build resource.
/v1/Services/{ServiceSid}/Builds/{Sid} - GETRetrieve a specific Function resource.
/v1/Services/{ServiceSid}/Functions/{Sid} - GETRetrieve a specific environment.
/v1/Services/{ServiceSid}/Environments/{Sid} - GETRetrieve a specific Build resource.
/v1/Services/{ServiceSid}/Builds/{Sid}/Status - GETRetrieve a specific Asset Version.
/v1/Services/{ServiceSid}/Assets/{AssetSid}/Versions/{Sid} - GETRetrieve a specific Function Version resource.
/v1/Services/{ServiceSid}/Functions/{FunctionSid}/Versions/{Sid} - GETRetrieve a specific log.
/v1/Services/{ServiceSid}/Environments/{EnvironmentSid}/Logs/{Sid} - GETRetrieve a specific Variable.
/v1/Services/{ServiceSid}/Environments/{EnvironmentSid}/Variables/{Sid} - GETRetrieve a specific Deployment.
/v1/Services/{ServiceSid}/Environments/{EnvironmentSid}/Deployments/{Sid} - GETRetrieve a the content of a specific Function Version resource.
/v1/Services/{ServiceSid}/Functions/{FunctionSid}/Versions/{Sid}/Content
How automating Twilio Serverless works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Twilio Serverless account.
- Grant access, then go live. You approve the specific Twilio Serverless operations it may use — and only those.
Automate Twilio Serverless with these
- Twilio199 operations
- Twilio Accounts13 operations
- Twilio Autopilot52 operations
- Twilio Bulkexports9 operations
- Twilio Chat40 operations
- Twilio Content6 operations
- Twilio Conversations101 operations
- Twilio Events22 operations
- Twilio Fax6 operations
- Twilio Flex50 operations
- Twilio Frontline2 operations
- Twilio Insights17 operations
Categories
Questions about Twilio Serverless automation
- Can HumDay connect to Twilio Serverless?
- Yes. HumDay reads Twilio Serverless's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 39 operations are documented.
- Do I need to write code to automate Twilio Serverless?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Twilio Serverless account.
- What can HumDay do in Twilio Serverless?
- 17 of the 39 documented operations change something in Twilio Serverless, and 22 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Twilio Serverless account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Twilio Serverless is held behind that approval.
Where this came from
The operations above are read from a published API description for Twilio Serverless at raw.githubusercontent.com/twilio/twilio-oai/main/spec/json/twilio_serverless_v1.json. Descriptions are the provider’s own words, not ours. Last published 2023-04-20.