AWS Transcribe and Placid Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build ai workflows between AWS Transcribe and Placid on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about AWS Transcribe and Placid

Detailed info you need to know about AWS Transcribe and Placid integrations in WEXTL. Explore which modules apps support and how you connect them.

  • AWS Transcribe

    • AI
    • 4 searches
    • 8 actions

    Transcribe audio and video files and manage custom vocabularies with Amazon Transcribe.[5]

  • Placid

    • AI
    • 1 trigger
    • 9 searches
    • 18 actions

    Creative automation that turns templates into images, PDFs and videos.[6]

How to connect AWS Transcribe to Placid

Set up your AWS Transcribe and Placid integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between AWS Transcribe and Placid work in WEXTL?

WEXTL exposes actions and triggers for AWS Transcribe and Placid that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Placid triggersAWS Transcribe actions

Placid modules

  • Create a Collection Groups templates into a new collection under a Title. Add up to 500 templates through Templates right away, and use Custom Data to store free text of up to 1024 characters.
  • Create a PDF Produces a PDF using a Template, and adds more pages through More Pages, each with its own template and typed layer values. Use Webhook URL to receive the finished file in another workflow.
  • Create a Template Use Title, Width and Height to set up a new template. Use Copy From Template to duplicate an existing one, which makes Placid replace the Title, Width and Height with those of the source. Use Add To Collections to file the new template in collections.
  • Create a Video Renders a video based on a Template, with extra clips from More Clips that each take their own template and audio. Use Audio URL to add a soundtrack and Frames Per Second to set the frame rate.
  • Create an Image Builds an image from a layered Template. Turn on Create Now to render at once instead of queueing, and use Extra Layer Values for properties such as geometry and opacity.
  • Delete a Collection Removes a collection of templates from Placid.
  • Delete a Font Deletes a custom font. Turn on Delete Even If In Use to remove a font that templates still use, which Placid otherwise refuses.
  • Delete a PDF Removes a generated PDF from Placid.
  • Delete a Template Deletes a single template from your Placid account.
  • Delete a Video Removes a video that was rendered earlier.
  • Delete an Image Deletes an image that Placid generated.
  • Get a Collection Gets the Title, Custom Data and Template IDs of one collection.
  • Get a Font Looks up one custom font. Turn on Include Account-Wide Fonts to reach fonts shared by your whole Placid account.
  • Get a PDF Reads the render state of a PDF. Use Fail If Not Finished to fail the run while it is unfinished. With it off, a render that ended in error is returned as data.
  • Get a Template Reads a template to get its Title, Tags and Layers.
  • Get a Video Looks up one video and returns its Status, File URL and any Error Code. Turn on Fail If Not Finished to stop the run while the video is still rendering.
  • Get an Image Checks the Status and File URL of one image. Turn on Fail If Not Finished to make the run fail until rendering is done, which suits an error handler that retries.
  • List Collections Lists collections along with the Template IDs they contain.
  • List Fonts Use Limit to set how many custom fonts are returned. Turn on Include Account-Wide Fonts to add the account-wide ones too.
  • List Templates Use Limit to cap how many templates are returned, keeping in mind that each 20 cost one request of your 60 per minute. Filter by Collection, Title Contains or Tag, and use Sort to order the results.
  • Make an API Call Makes an authorized free-form request to the Placid REST API with your saved credential.
  • Merge PDFs Use PDF URLs to supply 2 to 10 public PDF links, merged in the order given. Add Send to Amazon S3 to copy the merged file to your bucket.
  • Update a Collection Renames a collection with Title or edits its Custom Data. Use Add Templates and Remove Templates for single templates, or Replace Template List to swap the whole list.
  • Update a Font Renames a custom font through Title. The font file itself cannot be replaced.
  • Update a Template Sets new Tags, a Title or Custom Data on a template. Up to 10 tags are allowed and they replace the current ones. Use Clear Fields to empty chosen fields.
  • Upload a Font Adds a font file in ttf, otf, woff or woff2 format to your Placid fonts. Placid requires I Have The Right To Use This Font to be ticked. Use Title to give the font a name other than its file name.
  • Upload Media Uploads a File to Placid and returns its File URL. Placid keeps uploaded files only for a limited time.
  • Watch Finished Creatives Starts the workflow through a webhook as soon as Placid finishes an image, PDF or video, with its Status and the file link.

AWS Transcribe modules

  • Create a Vocabulary Builds a custom vocabulary in Amazon Transcribe, naming it with a Vocabulary Name for one Language Code. Give a list of Phrases or point Vocabulary File URI at a file, but not both.
  • Create a Vocabulary Filter Sets up a word filter for transcripts in one Language Code, saved as a Vocabulary Filter Name. Use Words for a short inline list, or Vocabulary Filter File URI for a stored one.
  • Delete a Transcription Job Deletes a transcription job from your Amazon Transcribe account.
  • Delete a Vocabulary Removes a custom vocabulary from Amazon Transcribe by its Vocabulary Name.
  • Get a Transcription Job Checks one transcription job by Transcription Job Name and returns the Transcription Job record Amazon Transcribe keeps for it.
  • Get a Vocabulary Looks up one custom vocabulary by Vocabulary Name and shows what Amazon Transcribe stores in its Vocabulary output.
  • List Transcription Jobs Browses the transcription jobs in your account and returns a Job Summary for each. Use Job Name Contains to match job names, Status to look at one stage, and Limit to set how many are listed.
  • List Vocabularies Lists the custom vocabularies in your Amazon Transcribe account. Use Name Contains to narrow by a name fragment, State Equals to match a processing state and Limit to bound the result.
  • Make an API Call Runs a free-form request against the AWS Transcribe REST API using your saved credential.
  • Start a Transcription Job Starts transcribing an audio or video file stored in S3, pointed to by the Media File URI inside Media. Set a Language Code, or turn on Identify Language to let Amazon Transcribe detect it. Use Output Bucket Name and Output Key to place the transcript.
  • Update a Vocabulary Changes an existing custom vocabulary. Provide new Phrases or a Vocabulary File URI together with the Vocabulary Name and Language Code.
  • Update a Vocabulary Filter Changes the terms of an existing filter, found by its Vocabulary Filter Name. Send new Words, or switch to the list at Vocabulary Filter File URI.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with AWS Transcribe and Placid integrations. Pick any from the list below if the current combination isn't the one you need.

Automate AWS Transcribe and Placid on WEXTL®

Claim your 3-day trial to build AWS Transcribe with Placid integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS Transcribe and Placid.

How do I connect AWS Transcribe and Placid?

Connect your AWS Transcribe and Placid accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between AWS Transcribe and Placid?

Example: when the "Watch Finished Creatives" trigger in Placid fires, WEXTL can "Create a Vocabulary" in AWS Transcribe. AWS Transcribe has 12 actions (including Create a Vocabulary, Create a Vocabulary Filter, and Delete a Transcription Job). Placid has 27 actions (including Create a Collection, Create a PDF, and Create a Template). Add filters and transforms between steps when you need them.[1]

Can AWS Transcribe trigger actions in Placid, and Placid in AWS Transcribe?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate AWS Transcribe and Placid?

No. AWS Transcribe-to-Placid automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does AWS Transcribe integrate with Placid in real time?

Yes. Trigger-based automations start the moment AWS Transcribe (or Placid) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a AWS Transcribe + Placid integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect AWS Transcribe with Placid?

You can build your AWS Transcribe + Placid automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the AWS Transcribe and Placid integration.

  1. AWS Transcribe and Placid integration source code, module specs and credentials implementation.
  2. Our AWS Transcribe and Placid integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for AWS Transcribe and Placid, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. AWS Transcribe integration information
  6. Placid integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted AWS Transcribe and Placid integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore AWS Transcribe and Placid, or get started