Ortto (Autopilot) and Beamer Integration

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

Build marketing workflows between Ortto (Autopilot) and Beamer 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 Ortto (Autopilot) and Beamer

Detailed info you need to know about Ortto (Autopilot) and Beamer integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Ortto (Autopilot)

    • Marketing
    • 4 triggers
    • 6 searches
    • 10 actions

    Manage contacts, accounts, audiences, and journeys in Ortto, formerly Autopilot.[5]

  • Beamer

    • Marketing
    • 4 triggers
    • 26 searches
    • 23 actions

    Product update feed, feature requests and NPS surveys.[6]

How to connect Ortto (Autopilot) to Beamer

Set up your Ortto (Autopilot) and Beamer integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Ortto (Autopilot) and Beamer work in WEXTL?

WEXTL exposes actions and triggers for Ortto (Autopilot) and Beamer 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.

Ortto (Autopilot) triggersBeamer actions

Ortto (Autopilot) modules

  • Archive Contacts Archives one or more contacts and reports how many were archived. A contact must be archived before it can be deleted.
  • Create a Custom Field Adds a custom field for people, with a Name and a Type of Text, Number or Date. The new Field ID is the output.
  • Create or Update a Contact Saves a contact matched on Email, creating it when it is new. Add Tags to label the contact and Fields for the rest of its data. Its Contact ID is returned afterwards.
  • Create or Update an Account Saves an account, creating it or updating the existing one. Add a Name and Domain, and use Fields for any other account data. Afterwards you receive the Account ID.
  • Delete Contacts Deletes contacts that are already archived and reports the count of removed contacts. Archive them first.
  • Get a Campaign Report Fetches the analytics report of one campaign, giving back its Campaign ID.
  • Get a Contact Finds one contact with its Email or Contact ID, returning only the requested Fields.
  • List Audiences Lists your marketing audiences by Audience ID and Name. Use Search term to find audiences by text, and Limit to read fewer.
  • List Campaigns Shows the campaigns and journeys running between a From date and a To date. Set Type to Journey or Campaign to see one kind.
  • List Contacts Pulls contacts that match a Filter, including only the requested Fields. Use Limit to read the first batch.
  • List Tags Returns the contact tags in your account, each with its Tag ID and Name. Use Limit to read only some.
  • Log an Activity Event Records custom activity events, up to 100 per call, that can trigger journeys. Send them as Activities, each with an Activity ID, an Email and Attributes.
  • Make an API Call Runs a free-form request against the Ortto (Autopilot) REST API using your saved credential.
  • Modify an Activity Definition Edits an activity definition identified by Activity ID, changing its Name or Attributes.
  • Subscribe or Unsubscribe a Contact to an Audience Changes audience membership for several People, each by Email with a Subscribed flag. Turn on SMS opted in to also record SMS consent.
  • Update a Custom Field Renames a custom field for people through Name, and gives the Field ID of the field that changed.
  • Watch Added Contacts Starts the workflow the moment a contact is added, with the Contact ID, Email and First name in the output. Ortto has no webhook subscription API, so paste the URL into a Webhook data source.
  • Watch Journey Entries Triggers instantly when a contact enters a journey. The Campaign ID and Email of the contact arrive with it.
  • Watch Journey Exits Triggers instantly as a contact leaves a journey, with the Campaign ID and First name of the contact.
  • Watch Updated Contacts Fires instantly when a contact changes and passes along the Contact ID, Last name and Email. The webhook URL is pasted into an Ortto Webhook data source.

Beamer modules

  • Check an NPS Prompt Asks Beamer if the NPS survey is due for one person at this moment. Describe the person via User ID, Email, Signup Date or Segment Filters, and give Current URL and Mobile for context. Output holds Should Show and a Survey URL.
  • Create a Feature Request Adds a feature request with a Title and Content, credited through Created By to a team member or an end user. Use Notes to keep an internal remark your users never see, and Visible to show it in your feed.
  • Create a Feature Request Comment Posts a reply under a feature request with Text. Add User ID, Email, First Name and Last Name to post as a specific person, and switch Visible on so your users see it.
  • Create a Feature Request Vote Casts a vote for a feature request on behalf of the person described by User ID, Email, First Name and Last Name. Output lists a Vote ID and a Voted time.
  • Create a Post Writes a feed post from a Title and Content. Turn on Publish Now to go live, or leave it off to save a draft. Set Publish Date to schedule it and use Category to label it Fix, Improvement or New.
  • Create a Post Comment Adds a comment beneath a post, with the Text you write attributed through User ID, Email, First Name and Last Name. Output gives the Comment ID with the Post Title.
  • Create a Post Reaction Leaves a Reaction under a post and, through User ID, Email, First Name and Last Name, records which person reacted. Output has the reaction identifier and the Created time.
  • Create a User Starts an analytics profile for a person in Beamer. Identify them by User ID or Email, then add Segment Filters, Language, Browser or Country as extra detail.
  • Delete a Feature Request Deletes a feature request from Beamer. This action cannot be undone.
  • Delete a Feature Request Comment Removes a reply someone left under a feature request.
  • Delete a Feature Request Vote Deletes a vote cast by one person for a feature request.
  • Delete a Post Removes a post from your Beamer feed. This cannot be undone.
  • Delete a Post Comment Removes a comment written beneath a post.
  • Delete a Post Reaction Deletes a reaction someone left against a post.
  • Delete User Data Removes all the data Beamer stores on the matching people, feedback and analytics included. Match people with User ID, Beamer ID or Email. This cannot be undone.
  • Delete Users Deletes the people matching User ID, Beamer ID or Email from Beamer. Several values can be separated by semicolons, and the removal cannot be undone. Output reports Deleted.
  • Get a Feature Request Looks up one feature request and returns its Status, Category, Votes and Comments.
  • Get a Feature Request Comment Fetches a comment from a feature request thread by Comment ID. Output has its Text, Written time, Visible flag and any Parent Comment.
  • Get a Feature Request Comment Count Gives a Count of the comments under a feature request. Supply Visible, Written After, Written Before or Search Text to tally a subset.
  • Get a Feature Request Count Counts feature requests across your account. Filters include Visible, Status, Category, Language and Search Text, plus a date range through Created After and Created Before.
  • Get a Feature Request Vote Reads a vote by Vote ID. Output gives the User Email and User First Name of the voter along with the Voted time.
  • Get a Feature Request Vote Count Returns the total votes that a feature request has gathered, without listing each voter.
  • Get a Feed URL Returns the address of your standalone feed as the URL output. Pass Language, Segment Filter or Theme to shape the feed, and User ID to attribute views to a person in analytics.
  • Get a Post Retrieves one post from your feed. Read it in another language through Language, and make its links trackable in Beamer Analytics with Traceable Links. Output includes Views, Clicks and Positive Reactions.
  • Get a Post Comment Pulls up one comment by Comment ID, with its Text, Written time and Post Title.
  • Get a Post Comment Count Shows how many comments a post has, narrowed by Written After, Written Before, Search Text or Language.
  • Get a Post Count Counts posts in your account and gives a Count. Use Published to separate live posts from drafts, and Archived, Expired, Category or Language to narrow it further.
  • Get a Post Reaction Looks up a reaction by Reaction ID and shows the Reaction kind, when it was Created and who left it.
  • Get a Post Reaction Count Counts reactions beneath a post, optionally only one Reaction kind or a window between Created After and Created Before.
  • Get an NPS Response Count Counts NPS survey responses and returns a Count. Set Lowest Score and Highest Score for a score band, Sent After and Sent Before for a period, or Search Text to match feedback.
  • Get an NPS Survey Link Builds an NPS survey link personalised with User ID, Email, First Name and Last Name. Output is the URL.
  • Get an Unread Post Count Counts the posts still unread by the person tracked under User ID or User Email. Output also gives the Feed URL and Popup URL.
  • Get Unread Posts Retrieves unread posts for the person identified by User ID or User Email. Turn on Mark As Read to flag the returned posts as read, which is off by default so workflows do not use up the unread state.
  • Invite a Team Member Invites someone to your Beamer team by Email and gives them a Role that sets what they can do in Beamer.
  • List Feature Request Comments Collects the replies under a feature request, each with Text, Written time and Team Member Email. Filter on Visible, Written After or Search Text, and bound the total with Limit.
  • List Feature Request Votes Retrieves the votes cast for a feature request, each with a Voted time and User Email. Restrict the period with Created After and Created Before.
  • List Feature Requests Returns feature requests along with Status, Votes and Comments. Main filters are Visible, Category and Search Text. Use Limit to set the number returned.
  • List NPS Responses Pulls NPS survey responses, each with its Score, Feedback and the person who sent it. Select a score band with Lowest Score and Highest Score, and use Limit as the cap.
  • List Post Comments Shows the comments left under a post. Trim them using Written After, Written Before or Search Text, and cap the count through Limit.
  • List Post Reactions Lists the reactions a post has received, each with its Reaction kind and Created time. Use Reaction to keep only one kind of reaction.
  • List Posts Fetches posts from your feed and narrows them with Published, Expired, Category or Archived. Use Limit to set the total.
  • List Users Finds people tracked in your Beamer analytics. Look up one person by User ID, Beamer ID or Email, and order them with Sort By on a field such as last seen.
  • Make an API Call Calls the Beamer REST API directly with a free-form request under your saved credential.
  • Remove a Team Member Deletes a Beamer team member, looked up by Email.
  • Send an NPS Email Survey Emails the NPS survey to the person at the Email address. Output contains a Status.
  • Update a Feature Request Changes a feature request: Title, Content, Visible, Status or Category. Use Created By to reassign the author. After a text change, resend all three text fields, Title, Content and Language.
  • Update a Post Edits an existing post. Turn Publish on to publish it or off to return it to a draft, and use Publish Date to reschedule. Changing any text or link means resending the full set: Title, Content, Language, Link URL and Link Text.
  • Update a Team Member Role Gives the team member with this Email a new Role in your Beamer team.
  • Update Users Updates every person that matches Match User ID, Match Beamer ID or Match Email. Set New User ID, New Email, First Name, Last Name or Language to change them.
  • Watch Events (Instant) Starts the workflow the moment Beamer reports an event. Depending on the event, the output has a Post ID, a Score and Feedback, or a Feature Request Title.

Explore alternative integrations

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

Automate Ortto (Autopilot) and Beamer on WEXTL®

Claim your 3-day trial to build Ortto (Autopilot) with Beamer integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Ortto (Autopilot) and Beamer.

How do I connect Ortto (Autopilot) and Beamer?

Connect your Ortto (Autopilot) and Beamer 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 Ortto (Autopilot) and Beamer?

Example: when the "Watch Added Contacts" trigger in Ortto (Autopilot) fires, WEXTL can "Check an NPS Prompt" in Beamer. Ortto (Autopilot) has 4 triggers (including Watch Added Contacts, Watch Journey Entries, and Watch Journey Exits). Beamer has 49 actions (including Check an NPS Prompt, Create a Feature Request, and Create a Feature Request Comment). Add filters and transforms between steps when you need them.[1]

Can Ortto (Autopilot) trigger actions in Beamer, and Beamer in Ortto (Autopilot)?

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 Ortto (Autopilot) and Beamer?

No. Ortto (Autopilot)-to-Beamer automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Ortto (Autopilot) integrate with Beamer in real time?

Yes. Trigger-based automations start the moment Ortto (Autopilot) (or Beamer) 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 Ortto (Autopilot) + Beamer 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 Ortto (Autopilot) with Beamer?

You can build your Ortto (Autopilot) + Beamer automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Ortto (Autopilot) and Beamer integration.

  1. Ortto (Autopilot) and Beamer integration source code, module specs and credentials implementation.
  2. Our Ortto (Autopilot) and Beamer integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Ortto (Autopilot) and Beamer, 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. Ortto (Autopilot) integration information
  6. Beamer integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Ortto (Autopilot) and Beamer integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Ortto (Autopilot) and Beamer, or get started