Connect BrowserAct and touchSMS to Build Intelligent Automations

Choose a Trigger

BrowserAct

When this happens...

Choose an Action

touchSMS

Automatically do this!

Actions and Triggers

When this happensTriggers

A trigger is an event that starts a workflow.

New SMS Received

New SMS Received

Triggers when your touchSMS account receives a new SMS and provides the message details (sender, text, time).

Request a new Trigger for BrowserAct

Do thisActions

Action is the task that follows automatically within your BrowserAct integrations.

Run Task From Template

Run Task From Template

Run a saved browser task

Get Workflow Details By ID

Get Workflow Details By ID

Get workflow details by ID

Create Contact

Create Contact

Add a new contact in touchSMS using a mobile number and optional details (first name, surname, email, group). Can update the contact if the number already exists.

Send SMS

Send SMS

Send a text message to the specified phone number using your approved sender ID.

Send Verification SMS

Send Verification SMS

Send an SMS verification code to a recipient using the touchSMS verification template.

Add Opt-Out Number

Add Opt-Out Number

Adds a mobile number to the touchSMS opt-out list to stop SMS delivery.

Request a new Action for BrowserAct

Need help building your workflow?

Get instant answers from our AI assistant or connect with a support specialist anytime.

Frequently Asked Questions

How do I start an integration between BrowserAct and touchSMS?

To start, connect both your BrowserAct and touchSMS accounts to viaSocket. Once connected, you can set up a workflow where an event in BrowserAct triggers actions in touchSMS (or vice versa).

Can we customize how data from BrowserAct is recorded in touchSMS?

Absolutely. You can customize how BrowserAct data is recorded in touchSMS. This includes choosing which data fields go into which fields of touchSMS, setting up custom formats, and filtering out unwanted information.

How often does the data sync between BrowserAct and touchSMS?

The data sync between BrowserAct and touchSMS typically happens in real-time through instant triggers. And a maximum of 15 minutes in case of a scheduled trigger.

Can I filter or transform data before sending it from BrowserAct to touchSMS?

Yes, viaSocket allows you to add custom logic or use built-in filters to modify data according to your needs.

Is it possible to add conditions to the integration between BrowserAct and touchSMS?

Yes, you can set conditional logic to control the flow of data between BrowserAct and touchSMS. For instance, you can specify that data should only be sent if certain conditions are met, or you can create if/else statements to manage different outcomes.