AWS SQS and BotStar Integration

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

Keep AWS SQS and BotStar matched by integrating their events and actions. When communication events happen in AWS SQS, update the BotStar automatically - without any line of code in visual workflow builder.

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

Learn about AWS SQS and BotStar

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

  • AWS SQS

    • Communication
    • 1 trigger
    • 7 searches
    • 17 actions

    Send, receive, and manage messages on Amazon SQS queues.[5]

  • BotStar

    • Communication
    • 1 trigger
    • 8 searches
    • 18 actions

    Chatbot builder for Messenger and web chat.[6]

How to connect AWS SQS to BotStar

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

How does the integration between AWS SQS and BotStar work in WEXTL?

WEXTL exposes actions and triggers for AWS SQS and BotStar 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.

AWS SQS triggersBotStar actions

AWS SQS modules

  • Add a Permission Lets other AWS accounts use a queue. Name the policy with Label, list the accounts under AWS Account IDs and the SQS actions to allow under Actions, such as SendMessage or ReceiveMessage.
  • Cancel a Message Move Task Stops a message move task that is still running. Paste the Task Handle or fill Source ARN to list the tasks of a queue. Returns the Approximate Number Of Messages Moved.
  • Change Message Visibility Sets a new visibility timeout between 0 and 43200 seconds on a message already received from a queue. Take the Receipt Handle from Receive Messages or Watch Queue Messages.
  • Change Message Visibility in a Batch Changes the visibility timeout for a batch of at most 10 messages you received. Entries take an ID that is unique within the batch, a Receipt Handle and a Visibility Timeout. Output splits results between Successful and Failed.
  • Create a Queue Makes a new SQS queue with a Queue Name of 1 to 80 characters. FIFO queues need a name ending in .fifo. Use Attributes to configure it and Tags to add cost-allocation tags. Returns the Queue URL.
  • Delete a Message Removes a message you received from a queue, which acknowledges that it was processed. Use Receipt Handle to point at the exact delivery.
  • Delete a Queue Deletes an SQS queue together with every message in it. This cannot be undone.
  • Delete Messages in a Batch Deletes up to ten processed messages from a queue with one call, using an ID per entry that is new to the batch plus its Receipt Handle. Entries that could not be deleted are reported under Failed.
  • Get a Queue URL Finds the URL of an existing queue from its Queue Name, not from a URL. Add the Queue Owner AWS Account ID when the queue belongs to another account. Returns the Queue URL.
  • Get the Attributes of a Queue Reads configuration and state values of a queue. Use Attribute Names to ask for All of them or for specific ones like ApproximateNumberOfMessages. The values arrive as Attributes.
  • List Dead Letter Source Queues Lists the queues that send their failed messages to one dead-letter queue, given as the Dead-Letter Queue URL. Amazon SQS returns up to 1000 Queue URL results per page.
  • List Message Move Tasks Shows the active and completed message move tasks for the queue with this Source ARN. The vendor caps Limit at 10 per call.
  • List Queue Tags Reads the tags assigned to a queue, returned as one Tags map because the call is not paginated.
  • List Queues Lists the SQS queues of your region, each as a Queue URL. Use Queue Name Prefix to keep only queues whose names start with a case-sensitive text, and Limit to control how many are fetched.
  • Make an API Call Calls the AWS SQS REST API directly with a free-form request under your saved credential.
  • Purge a Queue Deletes every message from a queue and keeps the queue itself. This cannot be undone.
  • Receive Messages Fetches messages from a queue, 10 at most. They are hidden from other consumers for the visibility timeout, so delete them afterwards to confirm processing. Use Wait Time Seconds for long polling and Max Number Of Messages to set the batch size.
  • Remove a Permission Deletes one permission policy from a queue, using the Label it was created with.
  • Send a Message Puts one message on a queue, carrying a Message Body of up to 256 KB. FIFO queues need a Message Group ID to keep order and a Message Deduplication ID unless they dedupe by content. Returns the Message ID and Sequence Number.
  • Send Messages in a Batch Posts up to 10 messages to a queue in a single request. Each of the Entries has a Message Body and an ID unique in the batch, with optional Delay Seconds, plus a Message Group ID for FIFO queues.
  • Set the Attributes of a Queue Changes queue settings like the Visibility Timeout, Message Retention Period or Redrive Policy, all passed inside Attributes. Use Delay Seconds and Maximum Message Size for delivery delay and size limits.
  • Start a Message Move Task Begins moving messages out of a dead-letter queue, identified by its Source ARN. Use Destination ARN to pick the target queue and Max Number Of Messages Per Second to throttle the move. Returns the Task Handle.
  • Tag a Queue Adds cost-allocation tags to a queue, or changes the value of tags that already exist. Pass each tag to Tags as a key and value pair.
  • Untag a Queue Removes cost-allocation tags from a queue. Use Tag Keys to list the keys to take off.
  • Watch Queue Messages Runs the workflow for each new message on a scheduled check of a queue, with its Message ID, Receipt Handle, Body and Attributes. Use Wait Time Seconds to wait for arrivals and Visibility Timeout to hide a received message for a set time.

BotStar modules

  • Create a Bot Sets up a new chatbot in your BotStar account under a Name of your choice.
  • Create a Bot Attribute Defines an attribute on a bot with a Data Type and an optional starting Value. Add Language Values for a separate value per language.
  • Create a CMS Entity Opens a content table in the CMS of your bot, and can seed it with columns. Add Fields to start with some already defined.
  • Create a CMS Item Saves a new row in a CMS entity. Use Field Values to fill its columns and Status to set the state.
  • Create a Custom User Attribute Registers an extra profile field for bot users, with an Attribute Name and a Type.
  • Create CMS Entity Fields Appends new columns to an existing CMS entity. Every entry of Fields has a unique name, a name and a data type.
  • Delete a Bot Attribute Deletes an attribute from a bot, in the draft only or in the draft and live version.
  • Delete a CMS Entity Removes a CMS entity, with all the items stored in it.
  • Delete a CMS Item Removes one record from a CMS entity of a bot.
  • Delete CMS Entity Fields Deletes several columns of a CMS entity at once.
  • Get a Bot Fetches one bot with its Bot ID, Name and Team Name.
  • Get a Bot User Looks up a person who talked to a bot, by the User ID shown in the bot conversation. The profile has Email, Birthday, Channel, Locale and Timezone.
  • Get a CMS Entity Pulls the definition of a CMS entity, meaning its Name and the Fields it holds.
  • Get a CMS Item Shows a single CMS row with its Name, Status and Entity ID, as stored in one entity of a bot.
  • List Bot Attributes Gathers the attributes defined on a bot, each with a Description, Value and Data Type. Use Limit to cap the count.
  • List Bots Collects the bots in your account, up to Limit. Each has a Bot ID and a Team Name.
  • List CMS Entities Enumerates CMS entities for a bot along with their Fields, up to Limit.
  • List CMS Items Retrieves the records stored in a CMS entity. Narrow them down by Name or Status, and use Limit for the count.
  • Make an API Call Makes an authorized free-form request to the BotStar REST API with your saved credential.
  • Publish a Bot Sends the current draft of a bot live for your audience.
  • Send a Message Delivers a Messenger message written as JSON in the BotStar message format. Add a Message Tag to reach someone outside the 24 hour window.
  • Update a Bot Attribute Modifies the Description or Value on a bot attribute. Use Value Type to say how the value is sent.
  • Update a Bot User Revises the stored profile of a user: First Name, Last Name, Email, Gender or Birthday. Use Custom Attributes to write your own attribute values as JSON.
  • Update a CMS Entity Changes the Name of an existing CMS entity within a bot.
  • Update a CMS Item Rewrites a CMS row with a changed Name, Status or Field Values.
  • Update CMS Entity Fields Alters existing columns of a CMS entity, with each item of Fields naming the unique name of the column to change.
  • Watch Events (Instant) Starts the workflow the moment BotStar sends an event, with its Event Type, Tag Name and User ID.

Explore alternative integrations

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

Automate AWS SQS and BotStar on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS SQS and BotStar.

How do I connect AWS SQS and BotStar?

Connect your AWS SQS and BotStar 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 SQS and BotStar?

Example: when the "Watch Queue Messages" trigger in AWS SQS fires, WEXTL can "Create a Bot" in BotStar. AWS SQS has 1 trigger (including Watch Queue Messages). BotStar has 26 actions (including Create a Bot, Create a Bot Attribute, and Create a CMS Entity). Add filters and transforms between steps when you need them.[1]

Can AWS SQS trigger actions in BotStar, and BotStar in AWS SQS?

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 SQS and BotStar?

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

Does AWS SQS integrate with BotStar in real time?

Yes. Trigger-based automations start the moment AWS SQS (or BotStar) 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 SQS + BotStar 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 SQS with BotStar?

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

References

List of sources used to gather information about the AWS SQS and BotStar integration.

  1. AWS SQS and BotStar integration source code, module specs and credentials implementation.
  2. Our AWS SQS and BotStar integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for AWS SQS and BotStar, 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 SQS integration information
  6. BotStar 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 SQS and BotStar integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore AWS SQS and BotStar, or get started