What AgentBlazer is and where it fits in Salesforce

AgentBlazer is a third-party application that integrates with Salesforce to automate customer service workflows and handle routine support tasks. It sits outside the core Salesforce platform but connects to your Salesforce instance through APIs and authentication, letting you route incoming messages, create cases, and respond to customers without manual intervention.

The integration works by pulling data from your Salesforce org, processing it through AgentBlazer's automation rules, and writing results back to your records. You do not install it directly into Salesforce the way you would a managed package — instead, you authorize it to access your Salesforce data and configure how it behaves.

Key Takeaways

  • AgentBlazer requires a Salesforce account with API access enabled and a user with System Administrator or equivalent permissions to set up the connection.
  • You create a connected app in Salesforce first, which generates the credentials AgentBlazer needs to authenticate and read your data.
  • The actual authorization happens on the AgentBlazer side, where you log in with your Salesforce credentials and grant permission for the integration.
  • After connection, you configure workflows and rules within AgentBlazer to define which messages trigger actions and what those actions should be.
  • Testing the connection and running a pilot workflow on a small set of records before full rollout prevents misconfigured automations from affecting your entire customer base.

Creating a connected app in your Salesforce org

Before AgentBlazer can talk to Salesforce, you need to create a connected app that acts as a bridge. Log in to your Salesforce org as a System Administrator, then go to Setup (the gear icon in the top right), and search for "App Manager" in the Quick Find box. Click New Connected App.

Fill in the basic information: give the app a name like "AgentBlazer Integration", enter your contact email, and check the box for Enable OAuth Settings. In the OAuth scopes section, add the scopes AgentBlazer needs — typically Access and manage your data (api), Perform requests on your behalf at any time (refresh_token, offline_access), and Access your basic information (id, profile, email, address, phone). Set the Callback URL to the one AgentBlazer provides in its documentation or setup guide.

Save the app. Salesforce will generate a Consumer Key and Consumer Secret — copy both of these and store them somewhere secure. You will need them when you authorize AgentBlazer.

Authorizing AgentBlazer to access your Salesforce data

Log in to your AgentBlazer account (or create one if you do not have one yet). Look for a settings or integrations section, then find the option to connect a Salesforce org. AgentBlazer will ask you for the Consumer Key and Consumer Secret you just copied from the connected app.

Paste those credentials into AgentBlazer's setup form. AgentBlazer will then redirect you to log in with your Salesforce credentials. Use the same Salesforce account you used to create the connected app — it must have System Administrator permissions. After you log in, Salesforce will show you a permission screen asking whether to allow AgentBlazer to access your data. Click Allow.

Once you authorize, AgentBlazer will confirm the connection is active. You should see a message indicating that your Salesforce org is now linked. If the connection fails, check that the Consumer Key and Secret are correct and that your Salesforce org has API access enabled (which is standard for most editions, but some sandboxes may have it disabled).

Configuring workflows and automation rules

With the connection live, you can now set up the automations that AgentBlazer will run. In AgentBlazer, go to the workflows or automation section and create a new workflow. Define the trigger — for example, "when a message arrives from a customer email address" or "when a case is created with a specific status".

Then set the actions: AgentBlazer can create a case in Salesforce, update an existing record, send a response to the customer, or assign the case to a queue. You can also add conditions — for instance, "only create a case if the message contains the word 'urgent'" or "only assign to the support queue if the customer is a premium account".

Save the workflow and review the settings. Most AgentBlazer setups include a test mode where you can send a sample message and watch the workflow execute without affecting real records. Use this to verify that the automation behaves as you expect before you turn it on for live traffic.

Testing the integration before going live

Before routing all incoming messages through AgentBlazer, run a pilot on a subset of your customer base or a specific email address. Create a test workflow that handles messages from a test email account you control, then send sample messages and check that the corresponding records appear in Salesforce with the correct data.

Verify that fields are mapping correctly — for example, that the customer's email address lands in the Email field and not in a custom field, and that the message body appears in the Description or a designated text field. Check that case assignments work as intended and that any automated responses are being sent to the right address.

If something is wrong — a field is empty, a case is assigned to the wrong queue, or a response is not being sent — go back into AgentBlazer and adjust the workflow. Do not enable the workflow for your full customer base until the test run produces the results you expect.

Monitoring and adjusting after launch

Once you turn on AgentBlazer for live traffic, check your Salesforce case queue regularly for the first week. Look for cases that AgentBlazer created and verify that the data is clean, assignments are correct, and no duplicate records are being generated. If you notice patterns — for example, all cases from a certain email domain are missing a field — adjust the workflow in AgentBlazer and test the fix with a new sample message.

AgentBlazer logs its actions, so if a workflow fails to execute, you can usually see why in the integration logs. Check these logs if cases stop appearing in Salesforce or if automations seem to have stopped running. Most issues are caused by a field mapping that no longer matches your Salesforce schema or a permission that was revoked.

Review your connected app permissions periodically. If AgentBlazer no longer needs a certain scope, you can remove it from the connected app settings in Salesforce. If you need to revoke AgentBlazer's access entirely, go to Setup, search for "Connected Apps", find AgentBlazer, and click Revoke.

Frequently Asked Questions

What permissions does AgentBlazer need in Salesforce?

AgentBlazer needs API access to read and write records. The user account that authorizes the connection must be a System Administrator or have a custom profile with API Enabled and the Create, Read, Update, and Delete permissions on the objects AgentBlazer will touch (usually Cases, Contacts, and Accounts). The connected app itself defines which scopes are granted.

Can I use AgentBlazer with a Salesforce sandbox?

Yes. Create a separate connected app in your sandbox, generate its own Consumer Key and Secret, and authorize AgentBlazer to your sandbox org instead of production. This lets you test workflows without affecting live customer data. When you are ready to move to production, create a new connected app there and re-authorize.

What happens if the connection between AgentBlazer and Salesforce breaks?

AgentBlazer will stop creating or updating records in Salesforce, but it will usually queue the messages or flag them for manual review. Check the integration logs in AgentBlazer to see what failed. The most common cause is an expired OAuth token — re-authorize AgentBlazer by logging in again with your Salesforce credentials. If that does not work, verify the connected app still exists in Salesforce and has not been revoked.

Can I map custom fields in AgentBlazer?

Yes. In the workflow configuration, AgentBlazer lets you specify which incoming data goes into which Salesforce field. You can map a customer's phone number to a custom phone field, a message subject to a custom topic field, or any other field your org uses. Make sure the field exists in Salesforce and that the connected app has permission to write to it.

How do I disconnect AgentBlazer from Salesforce?

Go to Setup in Salesforce, search for Connected Apps, find AgentBlazer, and click Revoke. This immediately revokes all access. You can also revoke it from AgentBlazer's side by disconnecting the Salesforce org in AgentBlazer's settings. Either action stops AgentBlazer from reading or writing to your Salesforce data.